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

From Tom Lane
Subject Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable
Date
Msg-id 20985.1201619422@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable  (Euler Taveira de Oliveira <euler@timbira.com>)
Responses Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
List pgsql-hackers
Euler Taveira de Oliveira <euler@timbira.com> writes:
> +1. If we go with 'enable_sync_seqcans' for 8.3, and in a future release 
> cycle we do test the cases Simon described above and we agree we need to 
> do a fine tune to benefit from this feature, we will need to deprecate 
> 'enable_sync_seqscans' and invent another one (sync_seqscans_threshold). 
> Looking at this perpective, IMHO we should go with the number (0.25) 
> instead of the boolean.

Surely the risk-of-needing-to-deprecate argument applies ten times more
strongly to a number than a boolean.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable
Next
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable