Re: [PATCHES] Additional global stats

2007-03-15 Thread Magnus Hagander
> > Here's a patch to add some more data to pg_stat_database. Turns out it > > was a lot easier than I thought - especially after reading Alvaros mail. > > Luckily I think he was wrong this time ;-) > > This seems like the wrong way to go about it. Why not compute these sums > on demand by scanni

Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite

2007-03-15 Thread Jan Wieck
On 3/15/2007 11:16 PM, Tom Lane wrote: Jan Wieck <[EMAIL PROTECTED]> writes: Attached is the completed patch that changes pg_trigger and extends pg_rewrite in order to allow triggers and rules to be defined with different, per session controllable, behaviors for replication purposes. The SPI_s

Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite

2007-03-15 Thread Tom Lane
Jan Wieck <[EMAIL PROTECTED]> writes: > Attached is the completed patch that changes pg_trigger and extends > pg_rewrite in order to allow triggers and rules to be defined with > different, per session controllable, behaviors for replication purposes. The SPI_savedplans part of this is pretty blet

Re: [PATCHES] remove psql support for ancient copy syntax

2007-03-15 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Andrew Dunstan wrote: >> The attached patch implements Tom's recent suggestion to abandon the >> undocumented psql support for ancient copy syntax. If there's no >> objection I will apply before long. > Just to clarify: this means that \copy will not

Re: [PATCHES] Additional global stats

2007-03-15 Thread Tom Lane
Magnus Hagander <[EMAIL PROTECTED]> writes: > Here's a patch to add some more data to pg_stat_database. Turns out it > was a lot easier than I thought - especially after reading Alvaros mail. > Luckily I think he was wrong this time ;-) This seems like the wrong way to go about it. Why not comput

[PATCHES] Additional global stats

2007-03-15 Thread Magnus Hagander
Here's a patch to add some more data to pg_stat_database. Turns out it was a lot easier than I thought - especially after reading Alvaros mail. Luckily I think he was wrong this time ;-) Does this seem like a reasonable way to do it, or did I miss something completely? //Magnus Index: doc/src/sg

Re: [PATCHES] remove psql support for ancient copy syntax

2007-03-15 Thread Alvaro Herrera
Andrew Dunstan wrote: > > The attached patch implements Tom's recent suggestion to abandon the > undocumented psql support for ancient copy syntax. If there's no > objection I will apply before long. Just to clarify: this means that \copy will not work when connected to servers older than 8.0,

[PATCHES] remove psql support for ancient copy syntax

2007-03-15 Thread Andrew Dunstan
The attached patch implements Tom's recent suggestion to abandon the undocumented psql support for ancient copy syntax. If there's no objection I will apply before long. cheers andrew Index: src/bin/psql/copy.c === RCS file: /cv

Re: [PATCHES] Synchronized Scan WIP patch

2007-03-15 Thread Jeff Davis
On Thu, 2007-03-15 at 08:27 +, Simon Riggs wrote: > On Wed, 2007-03-14 at 01:42 -0700, Jeff Davis wrote: > > SYNC_SCAN_REPORT_INTERVAL 100 > > Jeff, > > This will stop SeqScans from working with buffer recycling, unless we > put the recycle limit to more than 100. That was why I requested you

Re: [PATCHES] Synchronized Scan WIP patch

2007-03-15 Thread Simon Riggs
On Wed, 2007-03-14 at 01:42 -0700, Jeff Davis wrote: > SYNC_SCAN_REPORT_INTERVAL 100 Jeff, This will stop SeqScans from working with buffer recycling, unless we put the recycle limit to more than 100. That was why I requested you set this to 16, so we can use a recycle buffer of 32. -- Simon