[COMMITTERS] pgsql: Message style improvements
Message style improvements Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fae625e7b9824ec64f770904108089ff4fbcf093 Modified Files -- src/bin/pg_dump/pg_dump.c|6 +++--- src/bin/pg_dump/pg_restore.c |2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Clarify the documentation of the --with-ossp-uuid option
Clarify the documentation of the --with-ossp-uuid option Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/51ad1784ccf9c2a72238a50a314771e34721f1d3 Modified Files -- configure |3 +-- configure.in |2 +- doc/src/sgml/installation.sgml |9 + 3 files changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Put documentation of backslash commands back in alphabetical ord
Put documentation of backslash commands back in alphabetical order Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7920d033d8b580f00ede0628ee0b1c3a3f3c6b43 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 420 1 files changed, 209 insertions(+), 211 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Pull up isReset flag from AllocSetContext to MemoryContext struc
Heikki Linnakangas writes: > Pull up isReset flag from AllocSetContext to MemoryContext struct. This > avoids the overhead of one function call when calling MemoryContextReset(), > and it seems like the isReset optimization would be applicable to any new > memory context we might invent in the future anyway. > This buys back the overhead I just added in previous patch to always call > MemoryContextReset() in ExecScan, even when there's no quals or projections. Do you actually have any measurements that prove that? This seems like a rather ugly destruction of a modularity boundary in return for a hypothetical performance gain. I'm also concerned that you've probably added cycles on net to MemoryContextAlloc (where it's no longer possible to tail-call AllocSetAlloc), which could very easily cost more cycles on most workloads than could ever be saved by making MemoryContextReset a shade faster. regards, tom lane -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Make plpgsql provide the typmods for its variables to the main p
Make plpgsql provide the typmods for its variables to the main parser. Historically we didn't do this, even though we had the information, because plpgsql passed its Params via SPI APIs that only include type OIDs not typmods. Now that plpgsql uses parser callbacks to create Params, it's easy to insert the right typmod. This should generally result in lower surprise factors, because a plpgsql variable that is declared with a typmod will now work more like a table column with the same typmod. In particular it's the "right" way to fix bug #6020, in which plpgsql's attempt to return an anonymous record type is defeated by stricter record-type matching checks that were added in 9.0. However, it's not impossible that this could result in subtle behavioral changes that could break somebody's existing plpgsql code, so I'm afraid to back-patch this change into released branches. In those branches we'll have to lobotomize the record-type checks instead. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/219dfae4e1b0ca7cbc0b2f0f7740e01657964c07 Modified Files -- src/pl/plpgsql/src/pl_comp.c |8 +++-- src/pl/plpgsql/src/pl_exec.c | 72 - src/pl/plpgsql/src/plpgsql.h |5 ++- 3 files changed, 64 insertions(+), 21 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Put lists in sensible order
Put lists in sensible order Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/60497722ac6d69d8ff82fe328b0a128e73433bec Modified Files -- doc/src/sgml/information_schema.sgml | 14 +++--- 1 files changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Use the right pgsql for isolation tests.
Use the right pgsql for isolation tests. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b08ddf8c761cd596c4664dde1125f38a8757756f Modified Files -- src/test/isolation/Makefile |5 - 1 files changed, 4 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Use the right pgsql for isolation tests.
On 05/22/2011 05:58 PM, Andrew Dunstan wrote: Use the right pgsql for isolation tests. Of course, this should say "Use the right psql ...". cheers andrew -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Remove spurious underscore in name of isolation tester on MSVC.
Remove spurious underscore in name of isolation tester on MSVC. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a9b6519606a4a95ae8052f8414841d02bcfe4582 Modified Files -- src/tools/msvc/Mkvcbuild.pm |2 +- src/tools/msvc/vcregress.pl |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
