Re: session IDs

From: Kris Jurka <books(at)ejurka(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: session IDs
Date: 2004-02-03 14:18:10
Message-ID: Pine.LNX.4.33.0402030914080.15293-100000@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> >
> > Tom Lane wrote:
> >
> >> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> >>
> >>> I did think about using a cluster-wide sequence, if we can make such
> >>> a thing (might also be useful for system generated UIDs too).
> >>
> >> Not a good idea IMHO. If you do that, then there will be no such thing
> >> as a purely read-only transaction, because *every* transaction will
> >> include a nextval() call. That means even read-only transactions cannot
> >> commit till the disk spins.
> >>

A sequence could be used if it was created with a sufficiently large CACHE
value, so a read only transaction would only have to hit the disk if it
happened to be the one to hit an exhausted cache.

Kris Jurka

In response to

  • session IDs at 2004-02-03 14:00:43 from Andrew Dunstan

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-02-03 14:49:16 Re: [PATCHES] log session end - again
Previous Message Fabien COELHO 2004-02-03 14:06:43 Re: pg_restore bug in 7.4.1 ?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-02-03 14:49:16 Re: [PATCHES] log session end - again
Previous Message Andrew Dunstan 2004-02-03 14:00:43 session IDs