pg_ctl stop -m immediate on the primary server inflatessequences
in [PgSql]
|
Prev: В Э Д компании: особенности таможенного регулирования в рамках Таможенного союзаa
Next: testing HS/SR - 1 vs 2 performance
From: Boszormenyi Zoltan on 12 Apr 2010 04:07 Martijn van Oosterhout �rta: > On Sat, Apr 10, 2010 at 02:36:41PM +0200, Boszormenyi Zoltan wrote: > >>>> The above is quite reproducable, "pg_ctl stop -m immediate" >>>> "usually" inflated my serial sequence, but I had two occasions >>>> when not. The 69 -> 70 was one. The inflated increase is always 33: >>>> >>> AFAIKS sequences are pre-logged with 32 values to WAL to avoid >>> overhead. I suspect this is why you are seeing those gaps. >>> >> Then it should happen all the time, even with "-m fast" or "-m smart", no? >> > > Nope, because on a normal shutdown it writes out the actual value. When > you say "immediate" you mean "right now, don't bother with anything not > important", like for example gaps in sequences. You're essentially > crashing the DB. > > Have a ncie day, > OK, thanks for the info. -- Bible has answers for everything. Proof: "But let your communication be, Yea, yea; Nay, nay: for whatsoever is more than these cometh of evil." (Matthew 5:37) - basics of digital technology. "May your kingdom come" - superficial description of plate tectonics ---------------------------------- Zolt�n B�sz�rm�nyi Cybertec Sch�nig & Sch�nig GmbH http://www.postgresql.at/ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |