From: | "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de> |
---|---|
To: | "Sam Mason" <sam(at)samason(dot)me(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Monitoring the sequence cycles |
Date: | 2009-08-19 17:40:30 |
Message-ID: | C4DAC901169B624F933534A26ED7DF311F9C81@JENMAIL01.ad.intershop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> How about disabling cycling and doing your own monitoring?
> It seems a bit fiddly because sequence values are created "outside"
> of any transaction and hence if you write something into a logging
> table you're going to loose it if the transaction rolls back.
The sequences are expected to cycle a few times per year, I use them to generate Ids accross large timed tables that are dropped when obsolete.
I want to make sure that I have enough free Ids left...
I will probably implement a "fuzzy" monitoring while logging the current values on a regulary basis.
Thanks,
Marc Mmain
--
Sam http://samason.me.uk/
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2009-08-19 17:43:04 | Re: Requesting help on PostgreSQL Replication |
Previous Message | Christophe Pettus | 2009-08-19 17:27:50 | Re: Wich the best way to control the logic of a web application? |