threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Peter Eisentraut wrote:\n \n> The patch is pretty straightforward,\n> but does anyone else actually want this? Comments?\n \nI agree that the initdb name seems odd next to the other executable\nnames, but the functionality seems a little out of place to me in\npg_ctl. The other options all c... |
[
{
"msg_contents": "Hi,\n\nAttached is the latest version of this patch.\n\nI altered rewriting a bit (I've brought the problems with the previous \napproach up a couple of times before) and this version should have the \nexpected output in all situations. This patch doesn't allow you to use \nINSERT/UPDATE/DEL... |
[
{
"msg_contents": "Well, I was regretting missing the deadline for this CommitFest and\nthen realized today was only the 14th, so I finished this up while the\nkids were napping.\n\nI ended up not reusing the reloptions.c code. It looks like a lot of\nextra complexity for no obvious benefit, considering that t... |
[
{
"msg_contents": "Hi,\n\nDuring reviewing aggregates ORDER BY, I was reading spec and found\ndescription like:\n\n== snip ==\n\nOf the rows in the aggregation, the following do not qualify:\n— If DISTINCT is specified, then redundant duplicates.\n— Every row in which the <value expression> evaluates to the nul... |
[
{
"msg_contents": "I've put together a small patch to provide a schema name in an fk\nviolation in deference to the todo item \"Report the schema along table\nname in a referential failure error message\"\n\nThe error message only contains the schema if the table name being\nreferenced is non-unique or not pres... |
[
{
"msg_contents": "\nAfter some time thinking about the best way forward for Hot Standby, I\nhave some observations and proposals.\n\nFirst, the project is very large. We have agreed ways to trim the patch,\nyet it remains large. Trying to do everything in one lump is almost\nalways a bad plan, so we need to ph... |
[
{
"msg_contents": "After consulting with some other members of the community, I tried to\npost my fk error string patch to the current commitfest, but\nmistakenly posted it to the current commitfest, not the open one.\n\nWhen I tried to correct this by moving the patch to the open 2010-01\ncommitfest, I could n... |
[
{
"msg_contents": "Log Message:\n-----------\n/home/peter/commit-msg\n\nTags:\n----\nREL8_3_STABLE\n\nModified Files:\n--------------\n pgsql/src/backend/tsearch:\n wparser_def.c (r1.14.2.5 -> r1.14.2.6)\n (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tsearch/wparser_def.c?r1=1.14... |
[
{
"msg_contents": "\nAt Tom's suggestion I am looking at allowing use of parameter names in \nSQL functions instead of requiring use of $1 etc. That raises the \nquestion of how we would disambiguate a parameter name from a column \nname. Essentially, ISTM, we could use some special marker such as @ \n(c.f. SQL... |
[
{
"msg_contents": "We still need to decide what to do with queue full situations in the proposed\nlisten/notify implementation. I have a new version of the patch to allow for a\nvariable payload size. However, the whole notification must fit into one page so\nthe payload needs to be less than 8K.\n\nI have also... |
[
{
"msg_contents": "With some lazy Sunday slack, the 2009-11 CommitFest is now officially \nclosed. Due to a bumper crop of review volunteers, almost all patches \nare already assigned an initial reviewer. Here are the notable exceptions:\n\nSE-PostgreSQL/Lite: It's hard to find a reviewer willing to take on ... |
[
{
"msg_contents": "Hello\n\nI propose to add possibility to use psql variables as real query\nparameters. The goal of this proposal is simplification of creating\npsql based commands. Current using of psql variables based on\nsubstitution has large area of using, but has some risks. a) there are\npossible sql i... |
[
{
"msg_contents": "This query:\n\nselect random() from generate_series(1,10) order by random();\n\nproduces sorted output. Should it?\n\n-- \nAndrew (irc:RhodiumToad)\n",
"msg_date": "Mon, 16 Nov 2009 05:28:15 +0000",
"msg_from": "Andrew Gierth <andrew@tao11.riddles.org.uk>",
"msg_from_op": true,
... |
[
{
"msg_contents": "In the following query (used by psql to show attribute defaults)\n\nSELECT a.attname,\n pg_catalog.format_type(a.atttypid, a.atttypmod),\n (SELECT substring(pg_catalog.pg_get_expr(d.adbin, d.adrelid) for 128)\n FROM pg_catalog.pg_attrdef d\n WHERE d.adrelid = a.attrelid AND d.adnum = a.... |
[
{
"msg_contents": "Hi,\n\nI am using this code on 8.4/8.5, which works on 64-bit,\nbut segfaults on 32-bit Linux:\n\n oids[0] = TEXTOID;\n values[0] = lex;\n nulls[0] = false;\n ret = SPI_execute_with_args(\n (just_title ?\n \"SELECT ids FROM product.t_product_inv_titleonly WHERE w... |
[
{
"msg_contents": "Dear PostgreSQL developers,ￜ\n\nWe are researching the motivation factors of Open Source software \nprogrammers and would like to ask your cooperation in our large-scale \nresearch. The research is performed for the Amsterdam Business School of \nthe University of Amsterdam. Your participat... |
[
{
"msg_contents": "Hello\n\nour customer reports different result of to_timestamp function between\n8.3 and 8.4\n\nIt looks like to_timestamp returns some strange timezone value\n\npostgres=# select to_timestamp('00:00:00','HH24:MI:SS');\n to_timestamp\n─────────────────────────────────\n 0001-01-01 00... |
[
{
"msg_contents": "Tom Lane wrote:\n \n> I agree with Heikki that it would be better not to commit as long as\n> any clear showstoppers remain unresolved.\n \nI agree that it would be better not to commit as long as any of the\nfollowing are true:\n \n(1) There are any known issues which would break things fo... |
[
{
"msg_contents": "Hi Everyone,\n\nGiven a table \"Items\" with a PK \"item1\" and \"Qty\" - a numeric column\nI'd like to define a way in Postgres to insert when item11 doesn't\nexist already in \"Items\" and update the Qty by adding the new quantity\nto the existent when the item11 exists. What is a good appr... |
[
{
"msg_contents": "Hello\n\nnow - complete patch\n\nToDo:\n* enhance a documentation (any volunteer?)\n* check name for backslash command\n\nRegards\nPavel Stehule",
"msg_date": "Mon, 16 Nov 2009 23:01:44 +0100",
"msg_from": "Pavel Stehule <pavel.stehule@gmail.com>",
"msg_from_op": true,
"msg_su... |
[
{
"msg_contents": "\n-----BEGIN PGP SIGNED MESSAGE-----\nHash: RIPEMD160\n\n\nIs there any chance we can raise the default geqo_threshold from\nits current default of 12? This seems too low, as a modern Postgres\non modern hardware has no problem with 12 table joins. However, I have\nseen geqo causing trouble f... |
[
{
"msg_contents": "While looking over the writable cte patch I noticed queries.sgml has\nlots of things in the form \"<literal>FROM</>\". I tried various\ngoogles to see if </> is some kind of sgml/xml shorthand for close the\nlast opened tag. But alas, nothing found. Bad google foo?\n\nShould we change thos... |
[
{
"msg_contents": "Are there any plans to (is anybody working on) implement better\ntimezone support in postgresql\nfor 8.5 ? Specifically, store the timezone info -instead of just the\ntimestamp as UTC ?\nhttp://wiki.postgresql.org/wiki/Todo#Dates_and_Times\n\nHernán J. González\n",
"msg_date": "Tue, 17 No... |
[
{
"msg_contents": "Hi,\n\nThe attached patch adds support for DO clause in plpythonu. It was \nheavily inspired by the plperl and plpgsql inline handler code.\n\nI couldn't figure out how to get added files to show in git diff so the \ntwo files that this patch adds: expected/plpython_do.out and \nexpected/plpy... |
[
{
"msg_contents": "Hello,\n\nthis small patch add missing USING clause to OPEN FOR EXECUTE statement\n+ cleaning part of exec_stmt_open function\n\n\nsee http://archives.postgresql.org/pgsql-hackers/2009-11/msg00713.php\n\nRegards\nPavel Stehule",
"msg_date": "Tue, 17 Nov 2009 21:04:03 +0100",
"msg_from... |
[
{
"msg_contents": "Pavel submitted a patch to add typmods to function declarations, but there\nwas no prior design discussion and it desperately needs some. Let me try\nto summarize the issues that seem to need agreement.\n\nThe proposed patch allows optional typmods to be attached to the declared\nargument an... |
[
{
"msg_contents": "hernan gonzalez <hgonzalez@gmail.com> wrote:\n \n> I believe that this distinction between two realms: one related to\n> (say) \"physical time\" and the other to (say) \"civil date-time\", is\n> the key to put some order... conceptually, at least (I'm not\n> speaking about feasibility for now... |
[
{
"msg_contents": "\nHello\n\n\n This has been discussed in #postgresql and posted to -performance a \ncouple days ago, but no solution has been found. The discussion can be \nfound here: \nhttp://archives.postgresql.org/pgsql-performance/2009-11/msg00162.php\n\n I just finished implementing a \"search engine... |
[
{
"msg_contents": "\nHello\n\n\n This has been discussed in #postgresql and posted to -performance a\ncouple days ago, but no solution has been found. The discussion can be\nfound here:\nhttp://archives.postgresql.org/pgsql-performance/2009-11/msg00162.php\n\n I just finished implementing a \"search engine\" ... |
[
{
"msg_contents": "Hi,\n\nI noticed that some example functions don't contain the magic block and that\nleads to error while loading those examples in 8.2 or later.\n\nAttached is a patch that adds it. I also add some missing header file. Don't\nhave a strong opinion about backpatching it or not.\n\n\n-- \n Eu... |
[
{
"msg_contents": "\nLooking at how byteain detects whether the input it is passed is the new \nhex format escape or the old octal escape, it uses:\n\n char *inputText = PG_GETARG_CSTRING(0);\n if (inputText[0] == '\\\\' && inputText[1] == 'x')\n\nDoesn't this read off the end of inputText... |
[
{
"msg_contents": "Attached is a patch to perform parameter reference lookups by name in\nthe body of functions. I'm hesitant to put it in for the commitfest\nas is, without a couple of questions posed to the group:\n\n1. palloc needs no free? I suppose this is a general knowledge\nquestion, but it seemed to ... |
[
{
"msg_contents": "Hey,\n\nSo I ran across this today:\n\nCREATE OR REPLACE FUNCTION RETURN_LOTS(INT) RETURNS SETOF INT AS \n $$ \n SELECT generate_series(1,$1); \n $$ \nCOST 0.5 ROWS 50 SET work_mem TO '5MB' LANGUAGE 'SQL';\n\npostgres=# explain analyze select return_lots(10000000);\nQUERY PLAN ... |
[
{
"msg_contents": "I was just writing a syntical example and wanted to make sure it worked.\nI found this:\n\nCREATE OR REPLACE FUNCTION RETURN_LOTS(INT) RETURNS SETOF INT AS \n $$ \n SELECT generate_series(1,$1); \n $$ COST 0.5 ROWS 10000000 SET work_mem TO '5MB' LANGUAGE 'SQL';\n\npostgres=# explain ... |
[
{
"msg_contents": "So I went to investigate bug #5196: turned on log_destination = csvlog\netc, and restarted the postmaster. I got this on stderr:\n\n2009-11-18 20:08:52.104 EST : : LOG: loaded library \"passwordcheck\"\nNot safe to send CSV data\n\nThe first line is a consequence of having still got\nshared... |
[
{
"msg_contents": "Overview:\nPatch to make data output that includes newlines & wrapped lines\nconsistent with the headers for that data.\nLink: https://commitfest.postgresql.org/action/patch_view?id=220\n\nSubmission review:\n\t* is in context diff\n\t* applies cleanly to current HEAD\n\t* includes its own te... |
[
{
"msg_contents": "Hi,\n\nmy question is that what platform were these\nfunctions developed and tested?\n\nWe have come across a value that fails a NOT NULL\nconstraint upon INSERT under HP-UX/IA64, but not\nunder x86-64 Linux. The value in question is\n1.9999999999999998 assigned to a \"double\" variable.\nUnd... |
[
{
"msg_contents": "Hi,\n\n\"pg_restore --help\" gives this message for the --no-tablespaces parameter:\n\n --no-tablespaces do not dump tablespace assignments\n\nThe message should say \"restore\" and not \"dump\". You'll find a patch attached \nthat fixes this issue.\n\nThanks.\n\nRegards.\n\n\n-- \nG... |
[
{
"msg_contents": "Hi,\n\nIs it just me or the union test case fails in CVS head?\n\nmanu\n\n-- \nEmmanuel Cecchet\nAster Data\nWeb: http://www.asterdata.com\n\n",
"msg_date": "Thu, 19 Nov 2009 16:21:43 -0500",
"msg_from": "Emmanuel Cecchet <manu@asterdata.com>",
"msg_from_op": true,
"msg_subjec... |
[
{
"msg_contents": "Here's my latest patch. I'm going to submit to the open commitfest. (hrm, it's 189K compressed, should I just let people use git in the future?)\n\nKnown issues:\n\n - Documentation has gaps.\n - Code formatting/ws is not consistent with PG's.\n\n\nAny feedback would be appreciated.\n\n\nExce... |
[
{
"msg_contents": "Is there any actual reason why we are building without thread safety\nby default on most platforms? Seems I get asked that every time\nsomebody forgets to add a \"--enable-thread-safety\". Wouldn't it be\nmore logical to have that be the default, and provide\n\"--disable-thread-safety\" if th... |
[
{
"msg_contents": "Hi\n\nIt seems that pl/pgsql ignores the DEFAULT value of domains for local\nvariables. With the following definitions in place\n\ncreate domain myint as int default 0;\ncreate or replace function myint() returns myint as $body$\ndeclare\n v_result myint;\nbegin\n return v_result;\nend;\n... |
[
{
"msg_contents": "Hi\n\nWhile trying to come up with a patch to handle domain DEFAULTs in\nplpgsql I've stumbled across the following behavior regarding domain\nDEFAULTs and prepared statements.\n\nsession 1: create domain myint as int default 0 ;\nsession 1: create table mytable (i myint) ;\nsession 2: prepar... |
[
{
"msg_contents": "In testing the TRIGGER WHEN patch, I notice that pg_dump is relying on\npg_get_triggerdef(triggeroid, true) (ie, \"pretty\" mode) to dump\ntriggers. This means that trigger WHEN conditions will be dumped\nwithout adequate parenthesization to ensure they are interpreted the\nsame way when loa... |
[
{
"msg_contents": "Howdy folks,\n\nI have an application that works just fine in PG 8.3.\nWe've installed 8.4 on another machine to perform pre-\nmigration testing. When we tried to compile our ecpg\nstuff under 8.4 the first thing that caught us was an\nerror stating that the column name 'server' was causing\... |
[
{
"msg_contents": "Log Message:\n-----------\nAdd a WHEN clause to CREATE TRIGGER, allowing a boolean expression to be\nchecked to determine whether the trigger should be fired.\n\nFor BEFORE triggers this is mostly a matter of spec compliance; but for AFTER\ntriggers it can provide a noticeable performance imp... |
[
{
"msg_contents": "\nThe following bug has been logged online:\n\nBug reference: 5206\nLogged by: Alvaro Herrera\nEmail address: alvherre@postgresql.org\nPostgreSQL version: any\nOperating system: any\nDescription: wal_sync_method in stock postgresql.conf may be wrong\nDetails: \n\nJ... |
[
{
"msg_contents": "Hello,\n\nI am still thinking, about using DO statement from psql console. I am\nmissing any parametrisation. It could not be a problem. All pl have a\nsupport for parameters, we have a libpq function PQexecParams - so we\nneed only some \"USING\" clause. I propose following syntax (and using... |
[
{
"msg_contents": "From: David E. Wheeler <david@justatheory.com>\n\nAs I threatened when I reviewed hstore in the last two commit\nfests, I've finally seen may way to edit the documentation. This\nis mostly word-smithing, making sure that all `>`s are encoded,\nmaking sure that various text is properly tagged ... |
[
{
"msg_contents": "VACUUM FULL does a peculiar hack: once it's done moving tuples, and\nbefore it truncates the relation, it calls RecordTransactionCommit to\nmark the transaction as committed in clog and WAL, but the transaction\nis still kept open in proc array. After it's done with truncating and\nother clea... |
[
{
"msg_contents": "pg_regress compares expected and actual output using \"diff -w\"\n(a/k/a --ignore-all-space). We have always done this, and I think\nthe idea was to avoid getting a lot of useless diff noise when the\nonly real difference is that one column value in a tabular display is\nwider than expected.... |
[
{
"msg_contents": "Hi,\n\nISTM that there's a superfluous curly brace in print_path (which only\ngets compiled with -DOPTIMIZER_DEBUG.\n\nPatch attached.\n\nJan",
"msg_date": "Sun, 22 Nov 2009 13:04:12 +0100",
"msg_from": "=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer@wulczer.org>",
"msg_from_op": true,... |
[
{
"msg_contents": "Hi Magnus.\n\nIt is a thing left behind.:-)\nplease apply it. \nThanks!\n==\nlibpq.lib(ip.obj) : error LNK2019: 未解決の外部シンボル __imp__WSAIoctl@36 が関\n数 _pg_foreach_ifaddr で参照されました。\nlibpq.lib(ip.obj) : error LNK2019: 未解決の外部シンボル __imp__WSASocketA@24 が\n関数 _pg_foreach_ifaddr で参照されました。\n==\n\nRegard... |
[
{
"msg_contents": "Log Message:\n-----------\nRemove -w (--ignore-all-space) option from pg_regress's diff calls.\n\nWe have used -w for a long time as a means of reducing the reported diff\nvolume when one element of a result table isn't of the expected width.\nHowever, most of the time the results just pass a... |
[
{
"msg_contents": "Hi,\n\nThis should be simple, but for some reason I'm not quite sure what the\nsolution is. I want to be able to update the value of a column for rows\nthat have been updated. More specifically, if a row is updated, I want it's\nmodified_date column to be populated with the current time sta... |
[
{
"msg_contents": "I put the attached together a while ago and neglected to send it. \nBasically it includes the text of the query being explained in the \nexplain output.\n\nI think it's more important to include the query text when using \nauto_explain than in other explain uses, which is why I did it this wa... |
[
{
"msg_contents": "So last time I checked this wasn't possible (at least not that anyone\nhas told me). I'd like to be able to create constraints that aren't\ntied to a specific table/column.\n\nI think that the syntax would look something like this\n\nCREATE CONSTRAINT empty CHECK (VALUE = '\\0' );\n\nthis sho... |
[
{
"msg_contents": "Hi there,\n\nattached is a patch, which contains implementation of a red-black\ntree, a self-balanced implementation of binary tree. The main goal of\nthis patch is to improve creation time of GIN index in the corner cases.\nWhile creation, GIN collects data in memory in binary tree until ... |
[
{
"msg_contents": "Hi!\n\npatch implements operator class for GiST over points. Supported operations:\npoint << point\npoint >> point\npoint <^ point\npoint >^ point\npoint ~= point\npoint <@ box\nbox @> point\npoint <@ polygon\npolygon @> point\npoint <@ circle\ncircle @> point\n-- \nTeodo... |
[
{
"msg_contents": "Hi there,\n\nhttp://www.sigaev.ru/misc/knngist-0.11.tar.gz\n\nwe'd like to present contrib module for CVS HEAD, which contains implementation \nof knn (k nearest neighbourhood) search in PostgreSQL, see README.knngist for\ndetails. KNNGiST is an extension of existing GiST, which inherits most... |
[
{
"msg_contents": "Hi,\n\nI'd like to improve the way PL/Perl handles arrays as function input parameters. In PL/Perl arrays are passed as plain text strings, and getting a value of an array element requires additional perl code to parse that string. I'd like to make this easier by converting each postgresq arr... |
[
{
"msg_contents": "I have extended COPY to support using a UDF as a target instead of the\nnormal 'file' or STDOUT targets. This dovetails nicely with a couple\nof extensions I have also written for dblink for the purposes of\nenabling direct cross-node bulk loading and replication. Please\nperuse the patches... |
[
{
"msg_contents": "I'm reviewing SE-PgSQL patch and have some comments.\nhttps://commitfest.postgresql.org/action/patch_view?id=212\n\nForgive me, but I'm a novice of SELinux. Some of the comments\nand question might be nonsense.\n\n==== Patch overview ====\nThe patch itself is large (>13K), but more than half ... |
[
{
"msg_contents": "I've started work on the enhancements to plperl I outlined on pg-general\n(XXX thread)\nI have a working implementation of those changes, plus some performance\nenhancements, that I'm now re-working into a clean set of tested and\npolished patches.\n\nThis patch is a first step that doesn't a... |
[
{
"msg_contents": "Rewriting my frame support types patch to allow any expression in\nPRECEDING/FOLLOWING clause, I found the syntax below in PG conflicts:\n\nframe_extent: frame_bound { ... }\n | BETWEEN frame_bound AND frame_bound { ... }\n;\nframe_bound: UNBOUNDED PRECEDING { ... }\n | UNBOUNDED FOLLOW... |
[
{
"msg_contents": "Hi there,\n\nI have problem with CVS HEAD (noticed a week or so ago) - \npsql -l show garbage instead of -|+. Looks, like utf-8 symbols used\ninstead that ascii characters.\n\n List of databases\n Name Б■┌ Owner Б■┌ Encoding Б■┌ Collati... |
[
{
"msg_contents": "Today I was contacted by a Microsoft (!) developer Kamil who was working on\nissues in Linked Servers to PostgreSQL. He brought the following scenario:\nif a column is dropped then ordinal positions of remaining columns are\nreported incorrectly.\n\nHere is test scenario:\n1) create a table i... |
[
{
"msg_contents": "\nLockDatabaseObject() doesn't perform AcceptInvalidationMessages(), yet\nthere is no comment as to why this has been left out. I thought we\ncached more than just relation info in various places.\n\n-- \n Simon Riggs www.2ndQuadrant.com\n\n",
"msg_date": "Wed, 25 Nov 2009 06:59... |
[
{
"msg_contents": "I've put up a wiki page with the issues I see with the patch as it\nstands. They're roughly categorized by seriousness.\n\nhttp://wiki.postgresql.org/wiki/Hot_Standby_TODO\n\nNew issues can and probably will still pop up, let's add them to the\nlist as they're found so that we know what still... |
[
{
"msg_contents": "Hi,\n\nI know it's documented that CREATE TABLE ... AS SELECT ...\nand SELECT ... INTO TEMP ... returns \"0\" as number of\naffected tuples via PQcmdTuples().\n\nWhy?\nHow much work would it be to pass this info up?\n\nThe question arose because in ECPG, such statements\nlike the above return... |
[
{
"msg_contents": "\nRecent change:\n\nAn idle-in-transaction transaction can also hold a temporary file. Think\nof an open cursor, for example. Therefore, remove the distinction\nbetween CONFLICT_MODE_ERROR and CONFLICT_MODE_ERROR_IF_NOT_IDLE,\nidle-in-transaction backends need to be killed too when a tablespa... |
[
{
"msg_contents": "Attached is a patch which adds a chapter to git in our documentation,\naround where we have several chapters about cvs today. It also removes\na few very out of date comments about cvs (really, nobody has a 28k8\nmodem and does cvs over it today. Even your cellphone is orders of\nmagnitude fa... |
[
{
"msg_contents": "Hi\n\nI'm currently investigating how much work it'd be to implement arrays of\ndomains since I have a client who might be interested in sponsoring that\nwork.\n\nThe comments around the code handling ALTER DOMAIN ADD CONSTRAINT are\npretty clear about the lack of proper locking in that code ... |
[
{
"msg_contents": "Hello\n\nI was surprised with rounding relative not big value. Is it correct?\n\npostgres=# select 499188.546875::real;\n float4\n────────\n 499189\n(1 row)\n\nregards\n\nPavel Stehule\n",
"msg_date": "Wed, 25 Nov 2009 19:21:06 +0100",
"msg_from": "Pavel Stehule <pavel.stehule@gmail.c... |
[
{
"msg_contents": "collateindex.pl is stored in /usr/share/sgml/docbook/. Attached fix\nmodify docbook.m4 to find correct path.\n\nIt would be nice also backported the fix back at least to 8.2.\n\n\tThanks Zdenek",
"msg_date": "Wed, 25 Nov 2009 21:36:11 +0100",
"msg_from": "Zdenek Kotala <Zdenek.Kotala@... |
[
{
"msg_contents": "Last night we had the standby server in a PITR setup seemingly \nspontaneously believe it had recovered completely and startup a new \ntimeline; I'm running this information by you guys to see if what had \nhappened is considered a bug, or if there is a simple explanation.\n\nSo some quest... |
[
{
"msg_contents": "Hi there,\n\nI tried to force query to use index by specifying high execution cost, but\nwithout success, even seqscan cost doesn't changed. This is 8.4.1\n\n=# explain select count(*) from spots where coordinates <@ '(0,0),(0.1,0.1)'::box;\n QUERY PLAN \n--------... |
[
{
"msg_contents": "I ran across the subject issue and spent some time puzzling over it.\nIt seemed strange that the only backends which were holding open\ndeleted WAL files were ones where the connection was established\nwith a login which has no write permissions. Eventually, I vaguely\nrecalled there was suc... |
[
{
"msg_contents": "Hi,\n\nIn current SR, since a backup history file is not replicated,\nthe standby always starts an archive recovery without a backup\nhistory file, and a wrong minRecoveryPoint might be used. This\nis not a problem for SR itself, but would cause trouble when\nSR cooperates with Hot Standby.\n... |
[
{
"msg_contents": "When using the \"service\" parameter in a libpq connection (e.g., psql\nservice=foo), and the service name is not defined in pg_service.conf,\nthen the setting is silently ignored and the connection proceeds with\nwhatever other settings and defaults apply. That does not look very\nrobust. ... |
[
{
"msg_contents": "Updated application name patch, including a GUC assign hook to clean\nthe application name of any unsafe characters, per discussion.\n\nRegards, Dave\n\n-- \nDave Page\nEnterpriseDB UK: http://www.enterprisedb.com",
"msg_date": "Thu, 26 Nov 2009 15:50:15 +0000",
"msg_from": "Dave Page... |
[
{
"msg_contents": "I wrote a hackish little script that checks if all rules in ecpg.addons are\nindeed used to create the precompiler's parser to catch renamed symbol and\nsimilar changes. Now I wonder whether this should be added to the build\nprocess. If it is, the buildfarm will catch every such change, not ... |
[
{
"msg_contents": "The following commit to release-8.5.sgml:\n\nhttp://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e043393bcc7ed484c3e3cd6a1ce4c63651ab46be\n\nbroke the documentation (no end tag). Wouldn't the buildfarm notice\nthis, or does it not build the docs?\n\nRegards,\n\tJeff Davis\n\n",
... |
[
{
"msg_contents": "Hi Hackers,\n\nI've familiarized myself a little with the architecture of postgresql,\nlargely because it's interesting. There's one thing I can't quite\nfigure out though, and it seems that there's no better group of people\nin the world to ask about it.\n\nAt the lower levels in PG, reading... |
[
{
"msg_contents": "Recently openssl has been patched to not renegotiate keys.\n\nhttp://www.links.org/?p=780\n\n\nAfter a certain amount of data has gone through a postgresql connection\nthe server will attempt to switch session keys.\n\nWhat is the workaround (if any ) to avoid this in postgresql ?\n\nDave\n",... |
[
{
"msg_contents": "Now that I recognize the memory issue Andrew noted in his previous\nreview, I think we need to make a decision on this.\n\nhttp://archives.postgresql.org/message-id/876397c68t.fsf@news-spur.riddles.org.uk\n\nThe problem is that for current eval_windowaggregate the node holds\nwincontext to sa... |
[
{
"msg_contents": "Hi,\n I think this is more of code uniformity issue. Nevertheless, i just\nthought of putting it here.\n In the CommentCast function, i think both sourcetype and targettype\nshould be in the arguments, whereas in the code, source type is made as the\nname and the target type is passed in ... |
[
{
"msg_contents": "Hi,\n\nThe attached patch is offered for the 2010-01 commitfest.\nIt's also available in my git repository in the \"submitted\" branch:\n http://git.postgresql.org/gitweb?p=users/harriman/share.git;a=shortlog;h=refs/heads/submitted\n\nIn palloc.h and pg_list.h, some inline functions are def... |
[
{
"msg_contents": "---------- Forwarded message ----------\nFrom: rahimeh khodadadi <rahimeh.khodadadi@gmail.com>\nDate: 2009/11/29\nSubject: Re: psql+krb5\nTo: Denis Feklushkin <denis.feklushkin@gmail.com>\n\n\nThese items have added after my sending.\n\nI repeat again my configurations:\n\n\n*\n1) The configu... |
[
{
"msg_contents": "Hi,\n\nwhy we can't do $subject? it could have any benefit on the planner?\n\n-- \nAtentamente,\nJaime Casanova\nSoporte y capacitación de PostgreSQL\nAsesoría y desarrollo de sistemas\nGuayaquil - Ecuador\nCel. +59387171157\n",
"msg_date": "Mon, 30 Nov 2009 02:45:26 -0500",
"msg_from... |
[
{
"msg_contents": "Hi,\n\nAs far as I am aware, there is no way to tell when a user/role was granted\npermissions or had permissions revoked, or who made these changes. I'm\nwondering if it would be useful for security auditing to maintain a history\nof permissions changes only accessible to superusers?\n\nTha... |
[
{
"msg_contents": "Found this a couple of weeks back and just re-tested against head:\n\nCREATE TEXT SEARCH DICTIONARY with an empty thesaurus file will crasch \nthe backend.\n\nTo reproduce:\n$ echo \"\" > $(pg_config --sharedir)/tsearch_data/thesaurus_empty.ths\n\nThen use this thesaurus to create a text sear... |
[
{
"msg_contents": "Found this a couple of weeks back and just re-tested against head:\n\nCREATE TEXT SEARCH DICTIONARY with an empty thesaurus file will crasch \nthe backend.\n\nTo reproduce:\n$ echo \"\" > $(pg_config --sharedir)/tsearch_data/thesaurus_empty.ths\n\nThen use this thesaurus to create a text sear... |
[
{
"msg_contents": "Friendly greetings !\nI use postgresql 8.3.6.\n\nhere is a few info about the table i'm querying :\n-------------------------------------------------------------\n- select count(*) from _article : 17301610\n- select count(*) from _article WHERE (_article.bitfield && getbit(0)) : 6729\n\n\nHer... |
[
{
"msg_contents": "2009/11/30 张茂森 <maosen.zhang@alibaba-inc.com>:\n>\n\npgsql-hackers is not the right place for user questions; try\npgsql-general or pgsql-novice.\n\nThe answer to your question is in the documentation. You can find it here:\n\nhttp://www.postgresql.org/docs/8.4/static/transaction-iso.html#MV... |
[
{
"msg_contents": "It seems like the ordering of lexemes in tsvector has changed from 8.3\nto 8.4.\n\nFor example in 8.3.1,\n\npostgres=# select to_tsvector('english', 'quit everytime');\n to_tsvector \n-----------------------\n 'quit':1 'everytim':2\n\nThe lexemes are arranged by length and then by s... |
[
{
"msg_contents": "We've had many complaints about the fact that the regex functions\nare not bright about locale-dependent operations in multibyte character\nsets, especially case-insensitive matching. The reason for this, as\nwas discussed in this thread\nhttp://archives.postgresql.org/pgsql-hackers/2008-12/... |
[
{
"msg_contents": "Hi Everyone,\n\nWhere/What source can I modify to retrieve deleted records using HeapTupleSatisfiesVisibility()\n\nI am using postgres 8.1.11 source\n\nThe database has not yet been vacuumed.\n\nRegards,\nAllan\n\n\n \n",
"msg_date": "Mon, 30 Nov 2009 22:29:52 -0800 (PST)",
"msg_... |
[
{
"msg_contents": "Hello.\n\nThe following patches support Windows x64.\n\n1) use intptr_t for Datum and pointer macros. (to support Windows LLP64)\n almost the same as that post before.\n http://archives.postgresql.org/pgsql-hackers/2009-06/threads.php#01364\n\n2) use appropriate macro and datatypes for Wi... |
[
{
"msg_contents": "bruce wrote:\n> What might be interesting is to report CRC mismatches if the database\n> was shut down cleanly previously; I think in those cases we shouldn't\n> have torn pages.\n\nSorry, stupid idea on my part. We don't WAL log hit bit changes so\nthere is no guarantee the page is in WAL ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.