Prev: [HACKERS] testing HS/SR - 1 vs 2 performance
Next: [HACKERS] Virtual Private Database
From: Bernd Helmle on 10 Apr 2010 06:39


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

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Martijn van Oosterhout on 10 Apr 2010 16:02
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,
--
Martijn van Oosterhout <kleptog(a)svana.org> http://svana.org/kleptog/
> Patriotism is when love of your own people comes first; nationalism,
> when hate for people other than your own comes first.
> - Charles de Gaulle
 | 
Pages: 1
Prev: [HACKERS] testing HS/SR - 1 vs 2 performance
Next: [HACKERS] Virtual Private Database