From: Greg Stark <gsstark@mit.edu>
To: pgsql-general@postgresql.org
Subject: Re: Sequence Question
Date: 05 Aug 2004 11:07:40 -0400
Message-ID: <87r7qlipxf.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20040805041942.0D6513953@sitemail.everyone.net>
References: <20040805041942.0D6513953@sitemail.everyone.net>
Oscar Tuscon <obtuse@bmwe30.net> writes:
> I'm looking at ways to get batches of sequence values s faster. I don't want to set cache or increment to a large number for a variety of reasons. I need to grab id's in batches of varying numbers at various times, from 1 to several thousand at once.
> Doing it 1 at a time works, but more time goes into it than I'd like. I tried setting cache_value high but the database roundtrips were eating more time that I wanted to see; I only saw a 25% improvement in average time.
>
> SO... is the following approach safe? That is, will this be atomic, or is there a possibility that another connection could squeeze in a select nextval() between the select nextval() and the setval below?
> If it's safe I'd do this and take the sequences as the new currval - #I asked for (1500 or whatever).
>
> mydb=# select setval('my_id_seq', (select nextval('my_id_seq')+1500));
I'm not sure but I don't think that's safe since nextval doesn't lock the
sequence until the setval occurs. Though it might be unlikely to actually
occur in real life.
You could create a table with as many entries as you will ever need and then
select nextval() from that table and read all the records you get. That will
avoid the many round trips but it will still be slow since you will still have
to move all those individual values to your client.
Perhaps you should give up on the idea of using sequences at all.
If you have a table with one record (or one record per similar application).
You could "SELECT n FROM counters FOR UPDATE" the value in the record, then
"UPDATE counters SET n = n+?". It would serialize your accesses which would be
bad if you had lots of clients doing small increments, but if you have few
clients doing large increments it shouldn't be a problem.
Do make sure to vacuum this table frequently though.
--
greg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: gsstark@mit.edu
Subject: Re: Sequence Question
In-Reply-To: <87r7qlipxf.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox