On Mon, May 7, 2012 at 10:33 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Simon Riggs <simon@xxxxxxxxxxxxxxx> writes: >> On 7 May 2012 09:01, Vincent de Phily <vincent.dephily@xxxxxxxxxxxxxxxxx> wrote: >>> Would be nice to see it added to the documentation (unless I just didn't find >>> it ?), as it is quite surprising, and might lead to problems if people expect >>> to be able to read sequence values from the slave. > >> If you think so, please submit a patch. That's how it works here. > > Any documentation patch should be written by somebody who's actually > researched the behavior a bit; in particular I believe this can be > adjusted with the sequence CACHE setting. No. That behavior is caused by the hard-coded value SEQ_LOG_VALS (= 32 in sequence.c) rather than CACHE setting. Regards, -- Fujii Masao -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general