Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Date: 2008-01-31 01:41:20
Message-ID: 28144.1201743680@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Christopher BrowneDate: 2008-01-31 02:13:37
Subject: Re: [PATCHES] Better default_statistics_target
Previous:From: Bruce MomjianDate: 2008-01-31 01:38:31
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

pgsql-patches by date

Next:From: Christopher BrowneDate: 2008-01-31 02:13:37
Subject: Re: [PATCHES] Better default_statistics_target
Previous:From: Bruce MomjianDate: 2008-01-31 01:38:31
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group