From: | "rob" <rob(at)cabrion(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org>, <bmccoy(at)chapelperilous(dot)net> |
Subject: | currval was (Re: Re: Re: is PG able to handle a >500 GB Database? ) |
Date: | 2001-01-20 16:47:51 |
Message-ID: | 000a01c08300$bbb60200$4100fd0a@cabrion.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I use for sequences for row versioning not just numbering. I'm glad you
pointed this out. I'll need to revisit that code.
Is there a correct way to "initialize" currval without incrementing the
sequence?
--rob
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "rob" <rob(at)cabrion(dot)com>
Cc: "Florent Guillaume" <efgeor(at)noos(dot)fr>; "Oliver Elphick"
<olly(at)lfix(dot)co(dot)uk>; <pgsql-general(at)postgresql(dot)org>
Sent: Saturday, January 20, 2001 11:22 AM
Subject: Re: [GENERAL] Re: Re: is PG able to handle a >500 GB Database?
> "rob" <rob(at)cabrion(dot)com> writes:
> > currval returns error unless nextval has been called at least once in
the
> > session.
>
> > I use <seq>.last_value
>
> > Perhaps I'm fooling myself
>
> Yes, you are, unless you never have more than one client attached to
> your database. last_value will return whatever value was last assigned
> by any backend, therefore you might not get the value that was inserted
> into your tuple, but someone else's.
>
> The point about currval being initially undefined seems moot if what
> you're using it for is to recover the serial number that was assigned to
> a tuple you just inserted ...
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-20 16:51:53 | Re: currval was (Re: Re: Re: is PG able to handle a >500 GB Database? ) |
Previous Message | Tom Lane | 2001-01-20 16:42:37 | Re: Re: Re: is PG able to handle a >500 GB Database? |