threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Hi,\n\nlog file entries from running vacuumdb are \"double-spaced\",\nas vacuumdb ends the commands with \";\\n\" (cf. attached mini-\npatch). Is there a deeper meaning in that, or could it be\ntrimmed?\n\nTIA,\nTim",
"msg_date": "Tue, 27 Oct 2009 17:27:47 +0000",
"msg_from": "Tim Lan... |
[
{
"msg_contents": "Hello,\n\nI've been reading over the documentation to find an alternative to the\ndeprecated xpath_table functionality. I think it may be a possibility but\nI'm not seeing a clear alternative.\n\nThanks,\n\nChris Graner\n\nHello,I've been reading over the documentation to find an alternative ... |
[
{
"msg_contents": "\npg_read_file() takes byte-offset and length as arguments,\nbut we don't check the result text with pg_verify_mbstr().\nShould pg_read_file() return bytea instead of text or adding\nsome codes to verify the input? Only superusers are allowed\nto use the function, but it is still dangerous.\n... |
[
{
"msg_contents": "Folks,\n\nI'm looking at the \"developer docs\" on our site, and I couldn't find any\ndocs for the following features:\n\nColumn Triggers\nCalling Named Function parameters\nDEFAULT privileges\n\n... without docs, we really can't expect people to test them. Do we\nhave partial docs for these... |
[
{
"msg_contents": "Is there any interest in expanding \\dn+ to show schema size, similar \nto table sizes using \\dt+ in 8.4? We use separate schemas for each \nuser, so this would allow us to quickly look up the sizes of each \nuser's data.\n\nI have little experience with C and none with the PostgreSQL cod... |
[
{
"msg_contents": "While I'm fooling with the FOR UPDATE code ...\n\nCurrently, you can't apply FOR UPDATE to a relation that's on the inner\nside of an outer join, eg\n\nregression=# select * from a left join b using(aa) for update;\nERROR: SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an ... |
[
{
"msg_contents": "In http://archives.postgresql.org/message-id/26545.1255140067@sss.pgh.pa.us\nI suggested that we should push the actual execution (not just queuing)\nof non-deferred AFTER triggers into the new ModifyTable plan node.\nThe attached patch does that, and seems like a nice improvement since it\nr... |
[
{
"msg_contents": "I'd like to improve partitioning feature in 8.5.\nKedar-san's previous work is wonderful, but I cannot see any updated patch.\nhttp://archives.postgresql.org/message-id/bd8134a40906080702s96c90a9q3bbb581b9bd0d5d7@mail.gmail.com\n\nSo, I'll take over the work if there are no ones to do it.\nI'... |
[
{
"msg_contents": "I would like to add a temporal contrib module. The most important piece \nwould be adding a period data type and some support functions. Jeff \nDavis and I both have temporal projects on pgFoundry, and we've been \ncollaborating for a while. But there are some areas we'd like to get \nsome ad... |
[
{
"msg_contents": "Hello\n\nI got a possibility to continue on GROUPING SETS see\nhttp://wiki.postgresql.org/wiki/Grouping_Sets\n\nMy last patch was based on an sharing functionality with non recursive\nCTE. I would to recapitulate all options here and I would to prepare\nthis patch for next commitfest.\n\na) u... |
[
{
"msg_contents": "On Friday 30 November at 1200 GMT, the server that hosts our primary\nFTP server, GIT server and one of the website mirrors will be moved to\na new data center. Downtime is expected to be two to three hours.\n\nApologies for any inconvenience this may cause.\n\n-- \nDave Page\nEnterpriseDB UK... |
[
{
"msg_contents": "Hello to all,\nI'm a young programmer student, and I would like to realize TPR-index on\nPostgresql system. Of course I want to use GiST template, rather than\nwriting core :)\nI have some questions, and I would be very grateful if anybody answers my\nquestion.\n1) where could I know the prot... |
[
{
"msg_contents": "Dear,\n\nI have few suggestions about new features of postgresql.\n\n1.Replication and clustering\n\nincluded in core of postgresql\n\n\n2.other\n\nsupport beter olap and data warehouse solutions.\n\nsupport bulk load with c-api.\n\nthanks\n\nmarko\n\n\n \nDear,I have few suggestions abo... |
[
{
"msg_contents": "There is a gap in the permission scheme for inheritance setups. Say you\nhave this:\n\nCREATE TABLE persons (...);\nCREATE TABLE employees (...) INHERITS (persons);\n\nGRANT SELECT ON persons TO foo;\n\nThen user foo can extract who the employees are using\n\nSELECT * FROM persons EXCEPT SEL... |
[
{
"msg_contents": "We have two ways to copy table definitions:\n - CREATE TABLE child ( LIKE parent )\n - CREATE TABLE child ( ) INHERITS ( parent )\n\nBut \"INCLUDING xxx\" is supported only in \"LIKE\" version.\nShould we have \"INHERITS ( parent INCLUDING xxx )\" syntax ?\n\nWe can use LIKE and INHERITS at... |
[
{
"msg_contents": "Hi,\n\nUpdated Kedar's patch sending on behalf of Kedar.\n\n.tar.bz2 file contains files to be put at\n./src/include/catalog/pg_partition.h\n./src/backend/utils/partition\n./src/test/regress/sql/partition.sql\n\nThere are not toomany modifications. It includes improvements for validating\nmul... |
[
{
"msg_contents": "Hello\n\nI found some strange code. Is code in \"ELSE\" part dead, or its bug?\n\n\tif (stmt->returnType)\n\t{\n\t\t/* explicit RETURNS clause */\n\t\tcompute_return_type(stmt->returnType, languageOid,\n\t\t\t\t\t\t\t&prorettype, &returnsSet);\n\t\tif (OidIsValid(requiredResultType) && proret... |
[
{
"msg_contents": "Calling PL/Python's elog functions exposes some curious behavior. For\nexample, calling plpy.error('foo') prints\n\nERROR: ('foo',)\n\n(instead of the\n\nERROR: foo\n\nthat one might have hoped for.) This is an implementation artifact,\nbecause those functions don't check their arguments,... |
[
{
"msg_contents": ">> PARTITION BY RANGE ( a_expr )\n>> ...\n>> PARTITION BY HASH ( a_expr )\n>> PARTITIONS num_partitions;\n\n> Unless someone comes up with a maintenance plan for stable hashfunctions, we should probably not dare look into this yet.\n\nWhat would cover the common use case of per-day quals and ... |
[
{
"msg_contents": "Developers,\n\n I'm a senior developer for a small Company working on\nmodifications to both MySQL and PostgreSQL to support better\nusage reporting for DBAs. The project is called ExtSQL.\n\n Most of our work was originally done on MySQL and we've\njust gotten into PostgreSQL during... |
[
{
"msg_contents": "hello ...\n\nas my day has worked out quite nicely up to know i thought to f... it up \nand post a new concept which has been requested by a customer. the goal \nis to collect some feedback, ideas and so on (not to be mixed up with \n\"flames\").\nwe have funding for this and we are trying to... |
[
{
"msg_contents": "Hi,\n\nOne of our customers is running 8.2.14 and use a couple of pl/perl and \npl/perlu functions written by CMD. Everything worked normally until \nthey tried to call one particular pl/perl function from pl/perl via \nspi. It appears that a die call inside the callee just crashes the \n... |
[
{
"msg_contents": "I have discovered an obscure segfault condition in PL/Python. In\nPLy_output(), when the elog() call in the TRY branch throws an exception\n(this can happen when a statement timeout kicks in, for example), the\nPyErr_SetString() call in the CATCH branch can cause a segfault, because\nthe Py_... |
[
{
"msg_contents": "Hi,\n\nWhile playing around/evaluating tsearch I notices that to_tsvector is \nobscenely slow for some files. After some profiling I found that this is due \nusing a seperate TSParser in p_ishost/p_isURLPath in wparser_def.c.\nIf a multibyte encoding is in use TParserInit copies the whole rem... |
[
{
"msg_contents": "Hello, this is the first time I post on this list.\n\nI have setup a build environment on Windows 7 32 bits, with Visual Studio\n2005. Took me a while to get all the bits and parts working, but I finally\nwent through it. Only problem, I get 2 LINK errors:\nfatal error LINK 1104: cannot open ... |
[
{
"msg_contents": "I have completed the open issues (that I'm aware of) for operator\nexclusion constraints:\n\nhttp://archives.postgresql.org/message-id/1257101600.27737.159.camel@jdavis\n\nI'd now like to propose an extension to that feature: cardinality\nlimits.\n\nIt could go something like this (syntax sti... |
[
{
"msg_contents": "\nHi,\n\nIs there a reason not to remove backup_label automatically when crash recovery\nis run?\n\nereport in StartXLOG() says the folloing hint message, but I can't see other\ncases we have to take care;\n\n----\n\n ereport(PANIC,\n (errmsg(\"could not locate required checkpoint r... |
[
{
"msg_contents": "Hi,\n\nWhen a crash occurs before calling pg_stop_backup(),\nthe subsequent crash recovery causes the FATAL error\nand outputs the following HINT message.\n\n If you are not restoring from a backup, try removing the file\n\\\"%s/backup_label\\\".\"\n\nI wonder why backup_label isn't automa... |
[
{
"msg_contents": "Hi,\n\nRecently, the development of SR is not progressing because of\nthe indecision on whether walreceiver should be a subprocess\nof the startup process (i.e., a stand-alone program), or of\npostmaster. Since time is running out, I'd like to discuss\nabout this and advance the project.\n\nT... |
[
{
"msg_contents": "Hi guys,\nI hacked PostgreSQL 8.4.1 libpq and added a new function to specify\nresultFormat for individual result columns.\nAre you interested in a patch?\n\n(http://www.postgresql.org/docs/8.4/interactive/libpq-exec.html says:\nThere is not currently a provision to obtain different result co... |
[
{
"msg_contents": "One of the interesting properties of Oracle-compatible variable\nreferences in plpgsql is that the set of variables referenced by a\ngiven query could change during a forced replan. For example,\nconsider\n\n\tdeclare x int;\n r record;\n\t...\n\tfor r in select x,y from tab l... |
[
{
"msg_contents": "We had a discussion back in July about our maintenance policy and the\nupshot of that discussion was that there were relatively few\nobjections to dropping support for 7.4 - I believe Andrew Dunstan was\nthe only one who spoke against it, and it wasn't clear how strenuous\nhis objections were... |
[
{
"msg_contents": "Hello\n\nattached patch allows to store typmode for function parameters and\nfunction result. This patch is base for parametrised polymorphic types\nwhat was discussed moth ago.\n\nregards\nPavel Stehule",
"msg_date": "Tue, 3 Nov 2009 16:45:41 +0100",
"msg_from": "Pavel Stehule <pavel... |
[
{
"msg_contents": "Hi all,\n\nIt looks like Postgres has a restriction in DISTINCT ON queries where the DISTINCT ON expressions must match the left side of the ORDER BY list. The issue is that if a DISTINCT ON ... has multiple instances of a particular expression, this check doesn't seem to fire correctly.\n\nF... |
[
{
"msg_contents": "Is it an expected behavior?\n\n postgres=# CREATE TABLE t1 (a int, b int);\n CREATE TABLE\n postgres=# CREATE TABLE t2 (b int, c int);\n CREATE TABLE\n postgres=# CREATE TABLE t3 (d int) inherits (t1, t2);\n NOTICE: merging multiple inherited definitions of column \"b\"\n CREATE TABLE... |
[
{
"msg_contents": "Here is a patch to support arrays in PL/Python as parameters and return\nvalues. It converts an array parameter to a Python \"list\", and converts\na Python \"sequence\" return value back to an array.\n\nI have settled on two implementation restrictions for the moment:\n\n- Only supports one... |
[
{
"msg_contents": "\nI just run across an issue with ALTER TABLE and inheritance (i don't know \nwether this is of the same kind of issue KaiGai reported today, so i keep \nit on a separate thread).\n\nConsider the following workflow:\n\nCREATE TABLE foo(id integer NOT NULL, val text NOT NULL);\nCREATE TABLE fo... |
[
{
"msg_contents": "Hello\n\nactualised version: enhance check inside sql function\n\nRegards\nPavel Stehule",
"msg_date": "Wed, 4 Nov 2009 16:26:01 +0100",
"msg_from": "Pavel Stehule <pavel.stehule@gmail.com>",
"msg_from_op": true,
"msg_subject": "actualised funcs typmod patch"
},
{
"msg... |
[
{
"msg_contents": "Attached is a draft patch for the next step in my project of\nreimplementing plpgsql's parsing. This makes the recently added\nparser hooks accessible for callers that are using SPI (like\nplpgsql) and provides support for using such hooks in cacheable\nplans. As proof of concept, plpgsql i... |
[
{
"msg_contents": "A customer of ours recently hit a problem where after an autovacuum was\ncancelled on a table, the app started getting the message in $subject:\n\nERROR: could not read block 6 of relation 1663/35078/1761966: read only 0 of 8192 bytes\n\n(block numbers vary from 1 to 6). Things remained in ... |
[
{
"msg_contents": "Hello everyone,\n\nI was quite intrigued by a discussion that happened this past summer\nregarding generation of bootstrap files such as postgres.bki, and the\nassociated pain points of maintaining the DATA() statements in catalog headers.\nIt occurred to me that the current system is backwar... |
[
{
"msg_contents": "According to\nhttp://developer.postgresql.org/pgdocs/postgres/plpgsql-declarations.html#PLPGSQL-DECLARATION-RENAMING-VARS\nthe RENAME declaration in plpgsql has been known broken since PG 7.3.\nNobody has bothered to fix it. Shall we just rip it out?\n\nThe reason I'm looking at it right now... |
[
{
"msg_contents": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nHello\n\nWe have been using for years and without problems local ident\nautentification in the database for our user postgres.\n\nThese are the values that we have been using until version 8.3:\npg_hba.conf:\n- ------------\nlocal all ... |
[
{
"msg_contents": "An update on pg_comparator as an efficient way to do master-slave\nreplication.\n\nI have been using it for 2 years on a \"products\" table that has grown from\n12,000 rows to 24,000 rows. There are 3 slaves and 1 master. It is sync'ed\nevery 10 minutes.\n\nIt has never failed or caused pro... |
[
{
"msg_contents": "I'm planning to work on typed tables support. The idea is that you\ncreate a table out of a composite type (as opposed to the other way\naround, which is currently done automatically).\n\nCREATE TYPE persons_type AS (name text, bdate date);\n\nCREATE TABLE persons OF persons_type;\n\nOr the ... |
[
{
"msg_contents": "So I was testing the next step of plpgsql modification, namely actually\nletting the parser hooks do something, and it promptly blew up in\ntrigger functions, like so:\n\n+ ERROR: OLD used in query that is not in a rule\n+ LINE 1: SELECT OLD\n+ ^\n+ QUERY: SELECT OLD\n+ CO... |
[
{
"msg_contents": "Tom's recent work to fix the (TG_OP = 'INSERT' and NEW.foo ...)\nproblem reminded me of another PL/pgsql annoyance:\n\ncreate table foo (a integer);\ncreate or replace function broken() returns trigger as $$begin perform\n1; end$$ language plpgsql;\ncreate trigger bar after insert on foo for ... |
[
{
"msg_contents": "Hello,\n\nwe use a value -1 as two values: a) unknown typmod, b) unknown\nlocation. Can we substitute it by some better identifier?\n\nMaybe: UnknownTmod, UnknownLoc ... UnspecTmd, UnspecLoc???\n\nRegards\nPavel Stehule\n",
"msg_date": "Thu, 5 Nov 2009 23:17:31 +0100",
"msg_from": "Pa... |
[
{
"msg_contents": "I've been trying to make pl/perl support 8.5's inline functions, with the\nattached patch. The basics seem to be there, with at least one notable\nexception, namely that plperl functions can do stuff only plperlu should do. I\npresume this is because I really don't understand yet how plperl's... |
[
{
"msg_contents": "Hi there,\n\n\nI downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system. When I try to run autoconf on the source it tells me that I need autoconf-2.63. However the freeBSD ports only has autoconf-6.62.\n\nDoes anyone have any suggestion on how to resolve this? I posted a quest... |
[
{
"msg_contents": "The attached patch makes the basic cutover from inserting plpgsql\nvariables into SQL expressions by textual substitution, to handling\nthem via parser hooks. Currently I only have the pre_columnref hook\nwritten, so only the \"backwards compatible\" semantics are available.\nHowever this al... |
[
{
"msg_contents": "There is some code in the core parser to support the syntax\n\tUPDATE/DELETE ... WHERE CURRENT OF $n\nwhere $n is a parameter symbol. This was put in to support plpgsql,\nwith the expectation that $n would refer to a plpgsql cursor variable.\nNow that plpgsql is not doing textual insertion o... |
[
{
"msg_contents": "I believe we had consensus that plpgsql should offer the following three\nbehaviors when a name in a SQL query could refer to either a plpgsql\nvariable or a column from a table of the query:\n\t* prefer the plpgsql variable (plpgsql's historical behavior)\n\t* prefer the table column (Oracle... |
[
{
"msg_contents": "This is some oddness about the use of double quotes when defining\noperators in postgres 8.3. \n\nIt seems that the operator name in the create operator clause cannot be\nquoted, but in the commutator, or negator clauses, if schema-qualified,\nthe operator must be quoted. If not schema-qual... |
[
{
"msg_contents": "Me & Simon got talking about the difficulty of doing parallel pg_dump,\nwhere when you open multiple connections you must somehow ensure that\nall the connections use the same snapshot so that you get a consistent\ndump. We came up with a pretty simple way to do that:\n\n1. Open N+1 the conne... |
[
{
"msg_contents": "Hi,\n\nWhile checking some other code I used valgrind and noticed, as I had before, \nthat XLogInsert showed accesses to unitialized data.\nAfter some searching and playing around I found the source of that:\nheap_insert uses a struct xl_heap_insert which in turn has a xl_heaptid member \n- w... |
[
{
"msg_contents": "hi tom, sorry for the out-of-the-blue email (I'm not on the list)...\n\nOn Nov 6, 2009, at 12:21 PM, Tom Lane wrote:\n\n> I believe we had consensus that plpgsql should offer the following\n> three\n> behaviors when a name in a SQL query could refer to either a plpgsql\n> variable or a column... |
[
{
"msg_contents": "The next CommitFest is scheduled to start in a week. So far, it\ndoesn't look too bad, though a lot could change between now and then.\n\nI would personally prefer not to be involved in the management of the\nnext CommitFest. Having done all of the July CommitFest and a good\nchunk of the S... |
[
{
"msg_contents": "\n\n\n\n\nHi all,\n\nI am trying to compile PostgreSQL 8.3.8 on AIX 5.3 TL9 (64 bits).\nThe \".configure\" has been\nexecuted with success without any error but the compilation of\nPostgreSQL with \"gmake\"\nfails. \n\nPlease find below the errors I get : \nIn file included from\npsqlscan.c:2... |
[
{
"msg_contents": "I'm not sure if it can be finished until the start of the next CF, but\nI've been working on $subject. This work intends to extend current\nlimited frame types of window functions such like below;\n\n- ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING\n- ORDER BY x RANGE BETWEEN CURRENT ROW AN... |
[
{
"msg_contents": "I'm working on partitioning syntax, amd encountered a dependency issue.\nWhen we define partition, also create an implicit CHECK constraint.\nThe constraint should be kept until the pg_inherits entry is removed.\nBut we cannot have a dependency from the constraint to the inheritance.\n\n\nAn ... |
[
{
"msg_contents": "Hello, I would suggest the inclusion an option to create the database \naccent-insensitive,\nwithout need to use functions that in some cases it's slow to return the \nresult.\n\nExample:\nselect name from table where name ilike 'jo�o'\n\nReturn:\njo�o\njoao\nJOAO\nJO�O\n\nText by: Goog... |
[
{
"msg_contents": "Hi,\n\nWhile working on writeable CTEs, I noticed I have to special-case the\noutput of a Query node frequently because in INSERT/UPDATE/DELETE query\ntargetList is the target list which is used for modifying the result\nrelation and returningList is the output of that Query. However, this\n... |
[
{
"msg_contents": "Attached is the latest and greatest patch against CVS head, taken from\nthe hs-riggs branch in my git repository.\n\nThese two TODO items I listed earlier have now been fixed:\n\n> <done> allow connections after a shutdown checkpoint\n>\n> <done> don't clear locks belonging to prepared transa... |
[
{
"msg_contents": "I encountered the following log in 8.4.1 and HEAD. The deadlock occured\non the same object (relation 17498 of database 17497). Is it reasonable?\n\nERROR: deadlock detected\nDETAIL: Process 6313 waits for ExclusiveLock on relation 17498 of database 17497; blocked by process 6312.\n P... |
[
{
"msg_contents": "Robert Haas wrote:\n> The next CommitFest is scheduled to start in a week. So far, it\n> doesn't look too bad, though a lot could change between now and then.\n> \n> I would personally prefer not to be involved in the management of the\n> next CommitFest. Having done all of the July CommitF... |
[
{
"msg_contents": "Hi,\n\nI was using auto_explain to log plans (with analyze option on) from\nqueries that take more than 500ms, something i found i little odd is\nthat the duration says 779ms but actual time says 269ms (almost 3\ntimes lower), maybe some kind of instrumentation cleanup can explain\nthis?\n\n2... |
[
{
"msg_contents": "While reading through the patch for what must be the 100th time by now,\nit occurred to me that this comment in heap_xlog_freeze:\n\n+ /*\n+ * Freezing tuples does not require conflict processing\n+ */\n\nis plain wrong. In the master, we can freeze the xmin of a tuple tha... |
[
{
"msg_contents": "bruce wrote:\n> This brings up a concern I have --- that the number of patch\n> committers/managers is decreasing while our patch volume is increasing. \n> Consider that Heikki is working mostly on Hot Standby and Streaming\n> Replication, Alvaro isn't as involved in applying patches, Neil Co... |
[
{
"msg_contents": "Hi all,\n\nI have extracted the partitioning option for COPY (removed the error \nlogging part) from the previous patch. The documentation and test suite \nsample are provided as well.\nMore details are on the wiki page at \nhttp://wiki.postgresql.org/wiki/Auto-partitioning_in_COPY. Ignore th... |
[
{
"msg_contents": "Hello community,\n\n\nSecond time after migration 8.3.7 --> 8.4.1 I was caught by this\nproblem. Migration was 8 days ago.\n(note, I never seen such situation on 8.3)\n\nEnvironment:\n\nPostgreSQL 8.4.1 + patch\nhttp://archives.postgresql.org/pgsql-committers/2009-10/msg00056.php\nCentOS rele... |
[
{
"msg_contents": "Is it at all reasonable to try to create some mechanism so that\nexceptions (elog) that are caught and not rethrown do not end up in the\nlog? For example, when you write code that does something like\n\ntry\n insert\ncatch unique_constraint_violation\n update\nend try\n\nthis will end... |
[
{
"msg_contents": "Hi,\n\nAttached is a patch for a new listen/notify implementation.\n\nIn a few words, the patch reimplements listen/notify as an slru-based queue\nwhich works similar to the sinval structure. Essentially it is a ring buffer on\ndisk with pages mapped into shared memory for read/write access.\... |
[
{
"msg_contents": "Quoth the comments in nodeAgg.c:\n\n * We don't currently implement DISTINCT aggs for aggs having more\n * than one argument. This isn't required for anything in the SQL\n * spec, but really it ought to be implemented for\n * feature-completeness. FIXME someday.\n\nand:\n\n * DISTINCT alway... |
[
{
"msg_contents": "Hi,\n\nShould the standby also have to follow the WAL rule during recovery?\nThe current patch doesn't care about the write order of the data page\nand WAL in the standby. So, after both servers fail, restarting the\nex-standby by itself might corrupt the data.\n\nIf the standby follows the W... |
[
{
"msg_contents": "Folks,\n\nHere's expected behavior:\n\ndavidfetter@postgres=# SELECT array(values(1),(null));\n ?column? \n──────────\n {1,NULL}\n(1 row)\n\nThe next one is just plain unexpected. Either it's a bug, or it needs\nmore documentation in the function description in the docs, \\df+\noutput, etc.\... |
[
{
"msg_contents": "So I think we're agreed on adding a variable_conflict GUC for plpgsql.\nThe straight-and-narrow way to do it would be to make this a custom\nGUC that's defined only when plpgsql is dynamically loaded into the\nbackend. However that implies a lot of notational overhead, notably\nhaving to put... |
[
{
"msg_contents": "In a few days the 3rd 8.5 development CommitFest, 2009-11, is going to \nkick off, with the end goal being an alpha3 prerelease. If you have a \npatch in progress, you'll need to submit it before the deadline of \n2009-11-15 00:00:00 GMT for it to be considered during this round: \nhttp://w... |
[
{
"msg_contents": "Hi\n\nWhile trying to create a domain over an array type to enforce a certain\nshape or certain contents of an array (like the array being only\none-dimensional or not containing NULLs), I've stumbled over what I\nbelieve to be a bug in postgresql 8.4\n\nIt seems that check constraints on dom... |
[
{
"msg_contents": "Hello Everyone,\n\nI recently spent some time comparing the various techniques used to \nbackup/export MySQL, SQLite, and PostgreSQL databases. So far, pg_dump \nis the best tool I've used. I was well pleased with its efficient \nsyntax and functionality. However, I have two feature reques... |
[
{
"msg_contents": "Here's the patch to support Python >=3.1 with PL/Python. The\ncompatibility code is mostly in line with the usual 2->3 C porting\npractice and is documented inline.\n\nI needed to create an arguably weird hack to manage the regression\ntests. Instead of creating a new expected file for pret... |
[
{
"msg_contents": "consistently fails when compiled on ubuntu 9.10 here (on mini 10v).",
"msg_date": "Thu, 12 Nov 2009 20:53:57 +0000",
"msg_from": "Grzegorz Jaskiewicz <gj@pointblue.com.pl>",
"msg_from_op": true,
"msg_subject": "cvs head doesn't pass make check on one of the machines here"
},... |
[
{
"msg_contents": "The attached patch is a \"lite\" version of SE-PostgreSQL,\nfor the CommitFest#3.\n\nIts characteristic changes from the previous patches are\ndeveloper documentations and slimed-up code.\n\nThe developer documentation is a suggestion on the last\ncommit fest. In the CF#2, we worked to implem... |
[
{
"msg_contents": "Herewith a patch to implement agg(foo ORDER BY bar) with or without\nDISTINCT, etc. No artificial restrictions are imposed on what\nsyntactical combinations are allowed. However, ORDER BY is not allowed\nwith aggregates used as window functions (as per the existing\nrestriction on DISTINCT).\... |
[
{
"msg_contents": "Suppose you do this:\n\ncreate table animals (id serial primary key, name varchar not null);\n\nThen you can do this:\n\nwith beings as (select * from animals) select * from beings where id = 1;\n\nBut not this:\n\nwith beings as (select * from animals a1, animals a2) select * from\nbeings wh... |
[
{
"msg_contents": "The attached patch is a revised version of large object privileges\nbased on the feedbacks at the last commit fest.\n\nList of updates:\n* Rebased to the latest CVS HEAD\n* Add pg_largeobject_aclcheck_snapshot() interface.\n In the read-only access mode, large object feature uses\n query's ... |
[
{
"msg_contents": "Folks,\n\nShouldn't this work and produce a \"true?\"\n\nSELECT NULL IS NOT DISTINCT FROM ANY(ARRAY['a',NULL]);\nERROR: syntax error at or near \"ANY\"\nLINE 1: SELECT NULL IS NOT DISTINCT FROM ANY(ARRAY['a',NULL]);\n\nCheers,\nDavid.\n-- \nDavid Fetter <david@fetter.org> http://fetter.org/\... |
[
{
"msg_contents": "Attached patch fixed following warning:\n\n\"../../../src/include/nodes/parsenodes.h\", line 487: warning: enumerator\nvalue overflows INT_MAX (2147483647)\n\nThe reason is clear, enum is int not unsigned.\n\nIt is short fix, but I'm thinking about enum conversion to #define. We\nuse e.g. in ... |
[
{
"msg_contents": "Hi\n\nI'm currently working on a project where we need to build a global cache\ntable containing all values of certain types found in any of the other\ntables. Currently, a seperate insert, update and delete (plpgsql)\ntrigger function exists for each table in the database which is\nauto-gene... |
[
{
"msg_contents": "I just noticed that plpgsql's OPEN cursor FOR EXECUTE command lacks\na USING clause, so the only way to put parameters into the string is\ntextual insertion. Seems like an oversight, since every other variant\nof EXECUTE in plpgsql can do USING. Did we omit that intentionally?\n\n\t\t\trega... |
[
{
"msg_contents": "Attached is the patch against HEAD to support more frame types in\nwindow functions, including these frame types:\n\n- ROWS BETWEEN s PRECEDING AND e PRECEDING\n- ROWS BETWEEN s PRECEDING AND CURRENT ROW\n- ROWS BETWEEN s PRECEDING AND e FOLLOWING\n- ROWS BETWEEN s PRECEDING AND UNBOUNDED FOL... |
[
{
"msg_contents": "In GetSnapshotData(), we set subcount to -1 if the snapshot was overflowed:\n\n> \t\tsubcount = GetKnownAssignedTransactions(snapshot->subxip,\n> \t\t\t\t\t\t\t\t\t\t\t\t&xmin, xmax, &overflow);\n> \n> \t\t/*\n> \t\t * See if we have removed any subxids from KnownAssignedXids that\n> \t\t * w... |
[
{
"msg_contents": "Attached patch contains new dtrace probes for memory management. Main\npurpose is to analyze memory footprint - for example how many memory\nneeds transaction, peak memory per context, when memory block is reused\nor when it is allocate by malloc and so on.\n\nThere are three groups of probes... |
[
{
"msg_contents": "I'm apologize about my poor english\n\nI need to a \"double precision\" with magniude (ie meters, kilo, dolar, \netc). And can operate with them (ie dolar+dolar=dolar or \ndolar/dolar=double precision).\n\nDo you know some pluggin or module to do this?\n\nI can implement it but I need some ex... |
[
{
"msg_contents": "I attached patch which was already sent on february/april, but it was\nlost in time. It is originally from Robert Lor and Theo Schlossnagle.\n\nIt contains two DTrace probe groups. One is related to monitoring SLRU\nand second is about executor nodes.\n\nI merged it with the head.\n\nOriginal... |
[
{
"msg_contents": "First attempt at a docs patch for aggregate order by.\n\n-- \nAndrew.",
"msg_date": "Fri, 13 Nov 2009 23:49:11 +0000",
"msg_from": "Andrew Gierth <andrew@tao11.riddles.org.uk>",
"msg_from_op": true,
"msg_subject": "Aggregate ORDER BY docs patch, first attempt"
}
] |
[
{
"msg_contents": "It looks to me like the code in AlterSetting() will allow an ordinary\nuser to blow away all settings for himself. Even those that are for\nSUSET variables and were presumably set for him by a superuser. Isn't\nthis a security hole? I would expect that an unprivileged user should\nnot be a... |
[
{
"msg_contents": "There's a race condition between transaction commit and\nGetRunningTransactionData(). If GetRunningTransactionData() runs between\n the RecordTransactionCommit() and ProcArrayEndTransaction() calls in\nCommitTransaction():\n\n> \t/*\n> \t * Here is where we really truly commit.\n> \t */\n> \t... |
[
{
"msg_contents": "I'm just seeing these kind of compiler warnings in current HEAD:\n\npgstat.c: In function ‘pgstat_report_activity’:\npgstat.c:2276: warning: passing argument 1 of \n‘__dtrace_probe$postgresql$statement__status$v1$63686172202a’ discards \nqualifiers from pointer target type\n\nThere are more o... |
[
{
"msg_contents": "Andres Freund wrote:\nOn Saturday 14 November 2009 01:03:33 Kevin Grittner wrote:\n>> It is in context format, applies cleanly, and passes \"make check\".\n> Unfortunately the latter is not saying much - I had a bug there and\n> it was not found by the regression tests. Perhaps I should take... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.