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

Re: pg_ctl stop -m immediate on the primary server inflates sequences

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org
Cc: Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: Re: pg_ctl stop -m immediate on the primary server inflates sequences
Date: 2010-04-10 10:39:26
Message-ID: 16F3BE7D2A60E9334F1CD93C@amenophis (view raw or flat)
Thread:
Lists: pgsql-hackers

--On 10. April 2010 09:26:41 +0200 Boszormenyi Zoltan <zb(at)cybertec(dot)at> 
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.

-- 
Thanks

	Bernd

Responses

pgsql-hackers by date

Next:From: Joachim WielandDate: 2010-04-10 12:18:09
Subject: Re: a faster compression algorithm for pg_dump
Previous:From: Boszormenyi ZoltanDate: 2010-04-10 07:31:04
Subject: Re: pg_ctl stop -m immediate on the primary server inflates sequences

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