Horton

Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Simon Riggs <simon@2ndquadrant.com>, Neil Conway <neilc@samurai.com>, Gregory Stark <stark@enterprisedb.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, pgsql-hackers@postgresql.org
Date: 2008-01-31T01:41:20Z
Lists: pgsql-hackers 
Bruce Momjian <bruce@momjian.us> writes:
> Another question --- why don't we just turn off synchronized_seqscans
> when we do COPY TO?  That would fix pg_dump and be transparent.

Enforcing this from the server side seems a pretty bad idea.  Note that
there were squawks about having pg_dump behave this way at all; if the
control is on the pg_dump side then at least we have the chance to make
it a user option later.

Also, you forgot about pg_dump -d.

			regards, tom lane