threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Folks,\n\nI'm continuing in my efforts now to document how to deploy and manage\nreplication on our wiki. One of the things a DBA needs to do is to use\npg_current_xlog_location() (and related functions) to check how far\nbehind the master the standby is.\n\nHowever, there's some serious pro... |
[
{
"msg_contents": "Hi,\n\nA customer of ours has the need for temporary functions. The use case\nis writing test cases for their databases: the idea being that their\ncode creates a temp function which then goes away automatically at\nsession end, just like a temp table. It's said that this makes things\ngene... |
[
{
"msg_contents": "Fellow Hackers,\n\nI'm writing a function to turn an EXPLAIN plan into a table with columns. As such, I need to have a complete list of the various bits of each plan node and their types for the table. Here's what I've got so far:\n\n \"Node Type\" TEXT,\n \"Strategy\" ... |
[
{
"msg_contents": "Some time ago, CREATE CONSTRAINT TRIGGER was a deprecated command and it\nwas slated for obsolence or removal.\n\nRecent developments have turned it back into non-deprecated mode; it's\nnot going anywhere, and it needs to be fully documented.\n\nIt seems to me that it makes more sense to merg... |
[
{
"msg_contents": "I wondered why some of the buildfarm machines were showing\nmax_stack_depth = 100kB, and Andrew Dunstan kindly lent me the\nuse of \"dungbeetle\" to check it out. What I found out:\n\n1. max_stack_depth has the expected value (equal to ulimit -s)\nin any manually started postmaster. It only... |
[
{
"msg_contents": "\n(Prompted by a puzzled user on IRC)\n\nTen years ago, nearly, we made this commit \n<https://github.com/postgres/postgres/commit/8a2cdd77ad5c0a4f8902ea86d0377336e076abcb> \n(see what a good thing it is we carefully got all the history \ntransferred to git?)\n\nThe comment on the commit says... |
[
{
"msg_contents": "A customer of ours is quite bothered about finding zero pages in an index\nafter\na system crash. The task now is to improve the diagnosability of such an\nissue\nand be able to definitively point to the source of zero pages.\n\nThe proposed solution below has been vetted in-house at Enterpri... |
[
{
"msg_contents": "Since we now install PL/pgSQL by default, should we configure\nshared_preload_libraries to preload PL/pgSQL?\n\n-- \n Bruce Momjian <bruce@momjian.us> http://momjian.us\n EnterpriseDB http://enterprisedb.com\n\n + It's impossible for everything to be tru... |
[
{
"msg_contents": "\nPeter Eisentraut has suggested that we should run \"make -k\" instead of \nplain \"make\" for most or all of the buildfarm steps. This flag \nessentially instructs make to keep going rather than fail at the first \nerror. We haven't done that for the last five or six years that the \nbuildf... |
[
{
"msg_contents": "Sergey was kind enough to lend me use of buildfarm member dugong\n(IA64, Debian Etch) so I could poke into why its behavior in the\nrecursion-related regression tests was so odd. I had previously\ntried and failed to reproduce the behavior on a Red Hat IA64 test\nmachine (running RHEL of cou... |
[
{
"msg_contents": "I'm gradually slogging my way through the KNNGIST patches which were\nposted here:\n\nhttp://archives.postgresql.org/pgsql-hackers/2010-07/msg01183.php\n\nI have a couple of conceptual questions.\n\n1. Is KNNGIST intended to work if there's more than one pathkey? If\nso, how? Example:\n\nSE... |
[
{
"msg_contents": "Hey All,\n\nI just noticed that an editor at the w3c seems to have hit a wall with \nbrowser implementers,\nas they are all using Sqlite as their backend database, and so there is\nno second, independent implementation. (required for the standards process).\n\nAt some point, these specs will ... |
[
{
"msg_contents": "I've read this Peter's post:\n\nhttp://petereisentraut.blogspot.com/2010/04/news-from-sql-standard.html\n\nwhich says in SQL2011 has a new feature:\n\n> Combined data change and retrieval. PostgreSQL does something like this with RETURNING, but this feature is more elaborate and allows the wr... |
[
{
"msg_contents": "While designing writeable CTEs, I found it needs a new infrastructure\nthat helps to share the result data among separated PlannedStmt.\n\nUp to now, in a portal we only have multiple plans that share nothing\nbut relations, then executor starts, runs and ends separately.\nWriteable CTEs need... |
[
{
"msg_contents": " Buildfarm client version 4.3 has been released. It can be downloaded \nfrom <http://pgfoundry.org/frs/?group_id=1000040>\n\nChanges:\n\n *\n\n Add setnotes.pl, allowing users to set a note on their animals.\n\n *\n\n Support buildfarm client maintained git mirror, original s... |
[
{
"msg_contents": "Hi all,\n\nI've collected some interesting results during my experiments which I couldn't \nfigure out the reason behind them and need your assistance.\n\nI'm running PostgreSQL 9.0 on a quad-core machine having two level on-chip cache \nhierarchy. PostgreSQL has a large and warmed-up buffer\... |
[
{
"msg_contents": "I try to take problem of iteration over ROW or RECORD variable from a\ndifferent perspective. I would to design a solution where isn't\nnecessary a conversion from binary value to text (this is a\ndisadvantage of hstore based solution). This mean so we have to have a\nspecial instance of loop... |
[
{
"msg_contents": "We've got over 250GB of files in a pgsql_tmp directory, some with modification timestamps going back to August 2010 when the server was last restarted.\n\nselect pg_postmaster_start_time();\n pg_postmaster_start_time \n-------------------------------\n2010-08-08 22:53:31.999804-04\n(1 row)... |
[
{
"msg_contents": "\nThis is a reminder that at 8.00 a.m. tomorrow morning, my time, or \n2010-11-09 13:00 UTC, the buildfarm database server will be migrating to \na brand new 9.0 installation. It will be unavailable for up to about 6 \nhours.\n\ncheers\n\nandrew\n",
"msg_date": "Mon, 08 Nov 2010 18:00:53 ... |
[
{
"msg_contents": "I looked into the out-of-memory problem reported by Jakub Ouhrabka here:\nhttp://archives.postgresql.org/pgsql-general/2010-11/msg00353.php\n\nIt's pretty simple to reproduce, even in HEAD; what you need is an index\nexpression that computes a bulky intermediate result. His example is\n\n\tm... |
[
{
"msg_contents": "I don't think that this is a bug exactly, but it seems inconsistent.\n\nSee case below. After the item length gets changed, then when reading\nthe tuple later you get a t_len that includes padding.\n\nWe should document in a comment that t_len can mean multiple things. Or,\nwe should fix raw_... |
[
{
"msg_contents": "The attached patch provides plugin modules a hook just after object\ncreation time. In typical use cases, it enables to assign default\nsecurity labels on object creation by the external security providers.\n\nAs Robert suggested before, it provides a generic purpose main hook.\nIt takes an e... |
[
{
"msg_contents": "Alvaro Herrera wrote:\n> Excerpts from Charles Pritchard's message:\n \n>> I don't believe the webmaster is granted free rein:\n>> Disk quotas are enforced, data is separated per origin,\n>> hanging processes are up to the implementer, and postgres has\n>> plenty of settings for that.\n>\n> ... |
[
{
"msg_contents": "Hi,\n\nWhile executing the following command I got:\n\n$ pg_ctl init -D /tmp/foo -o \"-N 11\"\n/home/euler/pg/bin/initdb: invalid option -- N\nTry \"initdb --help\" for more information.\npg_ctl: database system initialization failed\n\nI tried \"-N 11\" (postgres option) after looking at the... |
[
{
"msg_contents": "Hi Everybody!\n\nI looked up this todo, and figured out a plan, how the implementation could\nbe written.\nThe main challenge is to keep constraints and indexes (for unique and PK\nconstraints) consistent.\nFortunately this is already realized in the case of an index. So at ALTER\nINDEX RENAM... |
[
{
"msg_contents": "We are facing a problem in dropping a tablespace after crash recovery. The\nrecovery starts from the last checkpoint, but the tables that were created\nby\na transaction in a tablespace before the checkpoint are still lying around;\nthe\ntransaction had not finished by the time of crash.\n\nA... |
[
{
"msg_contents": "I'm looking for some ideas on how to deal with the regression tests for\nthe per-column collation feature. These are the issues:\n\n* The feature only works on some platforms (tentatively: Linux,\nWindows).\n\n-> Possible solution: like xml test\n\n* The locale names are platform dependent, ... |
[
{
"msg_contents": "\nIt took a little longer than expected, due to a slightly clagged network \nbetween the old and new servers, but the database migration is complete \nand the server is back up and running.\n\ncheers\n\nandrew\n",
"msg_date": "Tue, 09 Nov 2010 17:25:19 -0500",
"msg_from": "Andrew Duns... |
[
{
"msg_contents": "We last researched index-only scans, also called covering indexes, in\nSeptember of 2008, but have made little progress on it since. Many have\nbeen waiting for Heikki to implement this but I talked to him and he\ndoesn't have time. \n\nI believe it is time for the community to move forward... |
[
{
"msg_contents": "Hi,\n\na question came to us in the form of a code example,\nwhich I shortened. Say, we have this structure:\n\n============================\nEXEC SQL BEGIN DECLARE SECTION;\n\nstruct t1 {\n int id;\n char t[80];\n};\ntypedef struct t1 t1_t;\n\nt1_t t1;\nEXEC SQL END D... |
[
{
"msg_contents": "> Peter Eisentraut wrote:\n> On tis, 2010-11-09 at 14:00 -0800, David E. Wheeler wrote:\n> \n>> I've been talking to Nasby and Dunstan about adding a\n>> Test::More/pgTAP-based test suite to the core. It wouldn't run\n>> with the usual core suite used by developers, which would continue\n>>... |
[
{
"msg_contents": "Hi all,\n\nThe discussion around wCTE during the last week or so has brought to my \nattention that we don't actually have a consensus on how exactly wCTEs \nshould behave. The question seems to be whether or not a statement \nshould see the modifications of statements ran before it. While ... |
[
{
"msg_contents": "Postgres supports ARRAY data types well, but there are some\nmore array functions in the SQL standard. Also, the standard\nhas MULTISET data type, that is an unordered array.\n\nIt looks easy to support additional array functions. There\nmight be some confusion to treat multi-dimensional arra... |
[
{
"msg_contents": "Hello list,\n\nSorry for not replying to the bug list, but I didn't receive that \nmessage. It's about\nhttp://archives.postgresql.org/pgsql-bugs/2010-11/msg00065.php\n\nThe test case there with remark about LBOUND is incorrect; we first \nfound the bug on a different result. In the process o... |
[
{
"msg_contents": "I've been thinking about supporting automatic replan of cached plans\nusing specific parameter values, as has been discussed several times,\nat greatest length in this thread:\nhttp://archives.postgresql.org/pgsql-hackers/2010-02/msg00607.php\nThere doesn't seem to be full consensus about wha... |
[
{
"msg_contents": "Hi,\n\nI' wondering if following delimited identifier brhavior is correct or\nnot:\n\ntest=# create table t1(i int);\ncreate table t1(i int);\nCREATE TABLE\ntest=# create table t1_foo(i int, j int);\ncreate table t1_foo(i int, j int);\nCREATE TABLE\ntest=# select * from t1;\nselect * from t1;... |
[
{
"msg_contents": "Hi all,\n\nSo today while I investigating some slow queries I found out that some time\nago some of our databases (due, innocently I suspect, to upgrades or\nhardware migrations) are now not using C as lc_ctype. And why some 'things'\ngot a lot slower...\n\nTo correct this problem it seems li... |
[
{
"msg_contents": "Markus Wanner wrote:\n \n> Note that dtester features a TAP reporter. However, the way Kevin\n> uses dtester, that probably won't give useful results. (As he uses\n> custom print statements to do more detailed reporting than TAP\n> could ever give you).\n \nAccording to the TAP draft standar... |
[
{
"msg_contents": "Markus Wanner wrote:\n \n> I stand corrected. Do you actually use the TapReporter?\n \nNo. I know so little about TAP that I wasn't aware that dtester\noutput was in the TAP format until I saw your post on this thread, so\nI went searching for the format to see what I might do to become mor... |
[
{
"msg_contents": "Markus Wanner wrote:\n \n> Well, there are three kinds of reporters: StreamReporter,\n> TapReporter and CursesReporter. By default, either curser or stream\n> is chosen, depending on whether or not dtester thinks its stdout is\n> a terminal or not.\n \n> The CursesReporter moves up and down ... |
[
{
"msg_contents": "Folks,\n\nFor the past couple of years, I've been hearing from the PostGIS\npeople among others that our type system just isn't flexible enough\nfor their needs. It's really starting to show its age, or possibly\ndesign compromises that seemed reasonable a decade or more ago, but\nare less s... |
[
{
"msg_contents": "mark wrote:\n \n> A \"fix\" being so that \"col LIKE 'foo%' \" could use btree indexes in\n> locales like en_US.UTF8 (and probably some others).\n \nHow about specifying an opclass?:\n \nhttp://www.postgresql.org/docs/current/interactive/indexes-opclass.html\n \n-Kevin\n",
"msg_date": "F... |
[
{
"msg_contents": "Improved parallel make support\n\nReplace for loops in makefiles with proper dependencies. Parallel\nmake can now span across directories. Also, make -k and make -q work\nproperly.\n\nGNU make 3.80 or newer is now required.\n\nBranch\n------\nmaster\n\nDetails\n-------\nhttp://git.postgresq... |
[
{
"msg_contents": "\"David E. Wheeler\" wrote:\n> On Nov 12, 2010, at 6:28 AM, Kevin Grittner wrote:\n \n>> I'll switch to TapReporter.\n>\n> Oh, that would be great, because I can then have the TAP stuff I\n> plan to add just run your tests and harness the results along with\n> everything else.\n \nI switched... |
[
{
"msg_contents": "This patch:\n\nhttp://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=bb0fe9feb9fd75a6aaa960028a9f810c883b0fc4\n\n...did not tidy up after itself as well as it might have. In\nparticular, it left the prototype for copydir() in src/include/port.h,\nwhile moving the source file from src/... |
[
{
"msg_contents": "Hi,\n\nStefan Kaltenbrunner reported a problem in postmaster via IM to me. I\nthought I had nailed down the bug, but after more careful reading of the\ncode, turns out I was wrong.\n\nThe reported problem is that postmaster shuts itself down with this\nerror message:\n\n2010-11-12 10:19:05 C... |
[
{
"msg_contents": "It's the time of year again where leaves are falling, temperatures \ndropping, and patches cry out looking for one last review before the \nstart of the holiday season. The patches submitted so far are listed at \nhttps://commitfest.postgresql.org/action/commitfest_view?id=8 , \nfeaturing a ... |
[
{
"msg_contents": "I wrote:\n \n> (1) Any idea why it finds the success of the tests unexpected?\n \nShould anyone else run into this, it's controlled by this in the test\nscheduling definitions (the tdef values):\n \n'xfail': True\n \nThere are other test flags you can override here, like 'skip' to skip\na tes... |
[
{
"msg_contents": "The attached patch allows the security label provider to switch\nsecurity label of the client during execution of certain functions.\nI named it as \"label switcher function\"; also called as \"trusted-\nprocedure\" in SELinux community.\n\nThis feature is quite similar idea toward security d... |
[
{
"msg_contents": "If a table has no indexes, we will always decide that any same-page\nupdate operation is a HOT update, since obviously it isn't modifying\nany indexed columns. But is there any benefit to doing so? I don't\nsee one offhand, and it has a downside: we're very likely to\nencounter broken HOT c... |
[
{
"msg_contents": "Circumstances have conspired to leave me with very little time to\nwork on the SSI patch during the last few weeks. I'm still convinced\nthat the work mentioned in this post is necessary to have a\ncommit-quality patch:\n \nhttp://archives.postgresql.org/pgsql-hackers/2010-10/msg01754.php\n ... |
[
{
"msg_contents": "Here is a series of three patches related to unlogged tables.\n\n1. The first one (relpersistence-v1) is a mostly mechanical patch that\nreplaces pg_class.relistemp (a Boolean) with pg_class.relpersistence\n(a character), so that we can support more than two values. BE SURE\nYOU INITDB, sinc... |
[
{
"msg_contents": "The goal of this work is to address all of the shortcomings of previous POSIX shared memory patches as pointed out mostly by Tom Lane.\n\nBranch: http://git.postgresql.org/gitweb?p=users/agentm/postgresql.git;a=shortlog;h=refs/heads/posix_shmem\nMain file: http://git.postgresql.org/gitweb?p=u... |
[
{
"msg_contents": "How about supporting something like:\n\nwal_keep_segments = '7d'\n\n-- \nScott Ribe\nscott_ribe@elevated-dev.com\nhttp://www.elevated-dev.com/\n(303) 722-0567 voice\n\n\n\n\n",
"msg_date": "Sun, 14 Nov 2010 10:38:36 -0700",
"msg_from": "Scott Ribe <scott_ribe@elevated-dev.com>",
"... |
[
{
"msg_contents": "I'm behind on my list mail so maybe this has been mentioned already, but \nwhen I just tried pg_stat_bgwriter from a build against today's HEAD I \ngot this:\n\npgbench=# select count(*) FROM pg_stat_bgwriter;\nERROR: did not find '}' at end of input node\n\nCan someone confirm if this broke... |
[
{
"msg_contents": "Attached patch adds some logging for each individual fsync call made \nduring a checkpoint, along with a summary at the end. You need to have \nthe following to see all of the detail:\n\nlog_checkpoints=on\nlog_min_messages=debug1\n\nAnd here's a sample:\n\nLOG: checkpoint starting: immedia... |
[
{
"msg_contents": "The attached patch adds a new field to pg_stat_bgwriter, counting the \nnumber of times backends execute their own fsync calls. Normally, when \na backend needs to fsync data, it passes a request to the background \nwriter, which then absorbs the call into its own queue of work to do. \nHow... |
[
{
"msg_contents": "This is the first of two patches for parallel pg_dump. In particular, this\npatch adds a new pg_dump archive type which can save pg_dump data to a\ndirectory, with each table/blob being a file so that several processes can\nwrite to different files in parallel.\n\nSince the compression is cur... |
[
{
"msg_contents": "Final patch in this series for today spreads out the individual \ncheckpoint fsync calls over time, and was written by myself and Simon \nRiggs. Patch is based against a system that's already had the two \npatches I sent over earlier today applied, rather than HEAD, as both are \nuseful for ... |
[
{
"msg_contents": "This is the second patch for parallel pg_dump, now the actual part that\nparallelizes the whole thing. More precisely, it adds parallel\nbackup/restore\nto pg_dump/pg_restore for the directory archive format and keeps the\nparallel\nrestore part of the custom archive format. Combined with my ... |
[
{
"msg_contents": "Here is the next patch in this epic series. [0]\n\nI have addressed most of the issues pointed out in previous reviews and\nremoved all major outstanding problems that were marked in the code. So\nit might just almost really work.\n\nThe documentation now also covers everything that's intere... |
[
{
"msg_contents": "This is an update to my earlier patch to add getrusage resource\ntracking to EXPLAIN ANALYZE.\n\nWith this patch you get something like:\n\n QUERY PLAN\n-------------------------------------------------------------------------------------------... |
[
{
"msg_contents": "I've spent a few hours pouring over the source code with\ncoarse-toothed comb, trying to figure out just exactly what might\nbreak if we changed MyDatabaseId after backend startup time, or in\nother words, allowed a backend to unbind from the database to which it\nwas originally bound and reb... |
[
{
"msg_contents": "Hello\n\nI try to implement SQL/PSM in PostgreSQL. I experimented with\nrewriting a plpgsql - you can check this implementation\nhttp://postgres.cz/index.php/SQL/PSM_Manual.\n\nI though so we can have some common PL stack. But I don't think it\nnow. It means a some more uglification of curren... |
[
{
"msg_contents": "We can rename each field in VALUES clause:\n\n=# SELECT * FROM (VALUES(123, 'ABC', NULL)) AS t(a,b,c);\n a | b | c\n-----+-----+---\n 123 | ABC |\n(1 row)\n\nBut I cannot find ways for ROW expression to do the same thing:\n\n=# SELECT ROW(123, 'ABC', NULL) AS (a,b,c);\nERROR: syntax erro... |
[
{
"msg_contents": "I keep wondering if there's a role for GPUs in Postgres and haven't\nfigure out how to integrate them yet but the day when we'll be\nexpected to exploit them seems to be getting nearer:\n\nhttp://aws.typepad.com/aws/2010/11/new-ec2-instance-type-the-cluster-gpu-instance.html\n\n-- \ngreg\n",
... |
[
{
"msg_contents": "Hi,\n\nI've been trying to summarise the last month of work into a single wiki\npage, to ease approaching the review of this now quite large patch. It\ntouches lots of things but the design and goal are simple enough to fit\nin my mind, that should be no problem for you guys here :)\n\n http... |
[
{
"msg_contents": "Remove outdated comments from the regression test files.\n\nSince 2004, int2 and int4 operators do detect overflow; this was fixed by\ncommit 4171bb869f234281a13bb862d3b1e577bf336242.\n\nExtracted from a larger patch by Andres Freund.\n\nBranch\n------\nmaster\n\nDetails\n-------\nhttp://git.... |
[
{
"msg_contents": "... and if so, isn't postmaster.c's code to transfer a HANDLE value to a\nchild process all wet?\n\n\tsprintf(paramHandleStr, \"%lu\", (DWORD) paramHandle);\n\n\t...\n\n\tparamHandle = (HANDLE) atol(id);\n\n\nBTW, it seems like it'd be a good thing if we had a Win64 machine in the\nbuildfarm.... |
[
{
"msg_contents": "I am attempting to test this\n\nhttps://commitfest.postgresql.org/action/patch_view?id=424\n\nbut I'm not sure which version of PG this should be applied to. (it would be really neat, on here:\nhttps://commitfest.postgresql.org/action/commitfest_view?id=8\nif there was a note that said, this... |
[
{
"msg_contents": "Is there a particular reason why track_functions is disabled by default?\n\nDoes having it at 'pl' by default create a noticable overhead for\npeople who aren't using pl functions? Or for that matter, even a\nnoticable overhead for those that *are*?\n\n-- \n Magnus Hagander\n Me: http://www.h... |
[
{
"msg_contents": "I've been trying to get clang working enough that I can at \nleast get HEAD going for a build farm client, and the attached \npatch is the bare minimum to get it working. There may be a \nbetter way to do this, but as indicated in a past thread, the \nGNU_SOURCE variable does not play nicely ... |
[
{
"msg_contents": "Magnus was just talking to me about having a better way of controlling\nmemory usage on autovacuum. Instead of each worker using up to\nmaintenance_work_mem, which ends up as a disaster when DBA A sets to a\nlarge value and DBA B raises autovacuum_max_workers, we could simply\nhave an \"auto... |
[
{
"msg_contents": "Following the discussions here \n(http://archives.postgresql.org/message-id/12375.1289429390@sss.pgh.pa.us), \nhere's a draft version of a rewrite of the GiST insertion algorithm and \nWAL-logging. The goal is to get rid of the tracking of incomplete splits \nand inserts in WAL replay, and th... |
[
{
"msg_contents": "Hello All,\n\n\nI am recently using sysbench with PostgreSQL 9.0 and 8.4.5 and doing\nsome tests on 8core systems with SSDs.\n\nI seem to be hitting some problems with the read-write tests and\nhoping to see if it is a possible concurrency bug or expected\nbehavior.\n\n\nUsing sysbench with ... |
[
{
"msg_contents": "I'd like to add information about whether or not a parameter or result can\npotentially be NULL to the RowDescription message.\n\nReason: I have the same reasons that Richard Jones did in 2006 (\nhttp://archives.postgresql.org/pgsql-interfaces/2006-01/msg00043.php). I'm\nwriting a Haskell lib... |
[
{
"msg_contents": "There might be inconsistency in overlap operators for array\ntypes ( <@, @>, and && ) when the argument arrays contain NULLs.\n\n- SELECT 2 = ANY (ARRAY[1, NULL]) => NULL\n- SELECT ARRAY[2] <@ ARRAY[1, NULL] => false\n\nNULL means \"unknown\" in definition, so should it return NULL\nrather ... |
[
{
"msg_contents": "Hi, Here is my review of 'rollback sequence reset for TRUNCATE ... RESTART \nIDENTITY' patch.\n\n- Is the patch in context diff format?\nIt's in git diff format. I guess it's OK ?\n\n- Does it apply cleanly to the current git master?\nYes\n\n- Does it include reasonable tests, necessary doc p... |
[
{
"msg_contents": "Hi,\n\nA customer of ours (Enova Financial) requested the ability to describe\nobjects in pg_depend. The wiki contains a simplistic SQL snippet that\ndoes the task, but only for some of the object types, and it's rather\nugly. It struck me that we could fulfill this very easily by exposing\... |
[
{
"msg_contents": "Currently, we overload \"indent\" meaning both \"unix socket\nauthentication\" and \"ident over tcp\", depending on what type of\nconnection it is. This is quite unfortunate - one of them being one of\nthe most secure options we have, the other one being one of the most\n*insecure* ones (real... |
[
{
"msg_contents": "Looking here:\n\n\thttp://wiki.postgresql.org/wiki/Working_with_Git\n\nthe script we recommend for doing context diffs for git,\ngit-external-diff, is not portable:\n\n\thttp://anarazel.de/pg/git-external-diff\n\nIt uses diff -L, which is not supported by FreeBSD, and I imagine many\nother op... |
[
{
"msg_contents": "See the attached test case. With that setup, this uses MergeAppend:\n\nexplain select * from ma_parent order by id limit 10;\n\nBut this one does not:\n\nexplain select * from ma_parent order by name limit 10;\n\n...which seems odd, because the index on ma_child1 and sorting the\nother two o... |
[
{
"msg_contents": "Hackers,\n\nI've been trying to diagnose in a production database why certain tables\nnever get autovacuumed despite having a substantial % of updates. The\nobvious reason is locks blocking autovacuum from vacuuming the table ...\nbut the trick is we don't log such blocking behavior, at all.... |
[
{
"msg_contents": "Hi,\n\nWhen I was reading vacuum.c, I found that the parameter 'stmttype' of\nget_rel_oids() is not used at all. The parameter had been used as\ncommand tag in the notice message about \"invalid object type\", but now\nsuch messages are reported by other functions.\n\nPlease find attached re... |
[
{
"msg_contents": "Hi all,\n\nI have a small problem: Suppose that I have a table in PostgreSQL which has\na integer field as its Primary key and I have used the Hash indexing method\nfor creating the index for the field on the table. Now I want to know the\nfollowing details about the index (assuming the machi... |
[
{
"msg_contents": "Hi,\n\nHere's a patch for showing in EXPLAIN ANALYZE the number of rows a plan \nqual filtered from a node's input. The output looks like this:\n\n\n QUERY PLAN \n\n-------------------------------------------------------------------------... |
[
{
"msg_contents": "Folks,\n\nI'd like to see about getting an enhanced UNNEST, first the one\naccording to the SQL standard, namely with an optional WITH ORDINALITY\nclause, and possibly some extra enhancements.\n\nIn order to get WITH ORDINALITY, would it be better to change gram.y\nto account for both WITH OR... |
[
{
"msg_contents": "Last month's new Linux kernel 2.6.36 includes a rewrite of the out of \nmemory killer: \n\nhttp://lwn.net/Articles/391222/\nhttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a63d83f427fbce97a6cea0db2e64b0eb8435cd10\n\nThe new \"badness\" method totals the task's ... |
[
{
"msg_contents": "---------- Forwarded message ----------\nFrom: Pavel Stehule <pavel.stehule@gmail.com>\nDate: 2010/11/18\nSubject: Re: patch: format function, next generation\nTo: Jeff Janes <jeff.janes@gmail.com>\nKopie: pgsql-hackers-owner@postgresql.org\n\n\nHello\n\nsomebody takes my oid :)\n\nupdated pa... |
[
{
"msg_contents": "Greg Smith wrote:\n \n> oom_adj is deprecated, scheduled for removal in August 2010:\n \nThat surprised me so I checked the URL. I believe you have a typo\nthere and it's August, 2012.\n \n-Kevin\n",
"msg_date": "Fri, 19 Nov 2010 07:13:45 -0600",
"msg_from": "\"Kevin Grittner\" <Kev... |
[
{
"msg_contents": "I am going through the Executor code and come across the following terms\nquite often. Can someone tell me what do they mean (in a few (may be a\ncouple of) sentences)?\n\n1. Scan State\n2. Plan State\n3. Tuple Projection\n4. EState\n5. Qual\n6. Expression\n\nThey sound quite ambiguous in the... |
[
{
"msg_contents": "Note the standard also supports unnesting multiple arrays concurrently, the rule for handling arrays with different lengths is to use null padding of the shorter array.\n\nSELECT * FROM\n UNNEST( ARRAY[5,2,3,4],\n ARRAY['hello', 'world'] )\n WITH ORDINALITY AS t(a,b,i);\n\na ... |
[
{
"msg_contents": "Hello\n\nI try to explicitly detoast a plpgsql var, but I this code breaks a content.\n\nwhat is wrong?\n\n switch (datum->dtype)\n {\n case PLPGSQL_DTYPE_VAR:\n {\n PLpgSQL_var *var = (PLpgSQL_var *) datum;\n\... |
[
{
"msg_contents": "Hi Dimitri and Joachim.\n\nI've looked the patch too, and I want to share some thoughts too. I've\nused http://wiki.postgresql.org/wiki/Reviewing_a_Patch to guide my\nreview.\n\nSubmission review:\n\nI've apllied and compiled the patch successfully using the current master.\n\nUsability revie... |
[
{
"msg_contents": "Hi,\n\nI am seeing the following here on 9.0.1 on Linux x86-64:\n\nLOG: redo starts at 1F8/FC00E978\nFATAL: too many KnownAssignedXids\nCONTEXT: xlog redo insert: rel 1663/16384/18373; tid 3829898/23\n\n\nand this is the complete history:\n\npostgres was running as HS in foreground, Ctrl-C... |
[
{
"msg_contents": "I was looking at KNNGIST some more today and found myself trying to\ndisentangle what match_clause_to_indexcol() is actually doing. It\nappears to me that the opfamily passed to that function is always the\nsame as index->opfamily[indexcol], which seems like needless\nnotational complexity. ... |
[
{
"msg_contents": "Hello,\n\nI last time added some features to JDBC driver meking in some way experimental \ndriver, it could be quite usefull, but if it's possible I would like to ask \nfor some reviews and tests. Maybe some ideas from this will be handly. \nBeacause the chageset is huge, I don't give patch s... |
[
{
"msg_contents": "Hi all,\n\nI'd like to revive Fernando Ike's patch implementing the \"\\dL\" command\nfor psql to list available languages, last version here:\n http://archives.postgresql.org/pgsql-hackers/2009-07/msg01092.php\n\nThe original patch produced columns \"Name\", \"Owner\", \"Procedural\nLanguag... |
[
{
"msg_contents": "format() function is very useful to construct formatted text,\nbut it doesn't support embedded formatter unlike sprintf() in C.\nOf course, we can use to_char() functions for each argument value,\nbut embedded formatter would be more readable.\n\nI'd like to propose %{...}s syntax, where form... |
[
{
"msg_contents": "Hello\n\nthis patch remove a multiple detoasting of varlena values in plpgsql.\n\nIt is usable mainly for iteration over longer array directly loaded\nfrom relation.\n\nIt's doesn't have a impact on semantic or behave - it's just eliminate\nsome performance trap.\n\nsample: table 10000 rows o... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.