Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable - Mailing list pgsql-hackers

From Michael Glaesemann
Subject Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Date
Msg-id 690C8C70-E633-46C3-BE0C-36F455F08636@seespotcode.net
Whole thread Raw
In response to Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jan 27, 2008, at 21:04 , Tom Lane wrote:

> [ redirecting thread to -hackers ]
>
> Neil Conway <neilc@samurai.com> writes:
>> On Sun, 2008-01-27 at 21:54 +0000, Gregory Stark wrote:
>>> I liked the "synchronized_sequential_scans" idea myself.
>
>> I think that's a bit too long. How about "synchronized_scans", or
>> "synchronized_seqscans"?
>
> We have enable_seqscan already, so that last choice seems to fit in.

Would it make sense to match the plural as well?

Michael Glaesemann
grzm seespotcode net




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pl/pgsql Plan Invalidation and search_path
Next
From: "Merlin Moncure"
Date:
Subject: Re: pl/pgsql Plan Invalidation and search_path