Re: pg_dump future problem. - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_dump future problem.
Date
Msg-id 5.1.0.14.0.20030505144032.02ab2750@mail.rhyme.com.au
Whole thread Raw
In response to Re: pg_dump future problem.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump future problem.
List pgsql-hackers
At 10:10 AM 4/05/2003 -0400, Tom Lane wrote:
>And the is_called flag fits into this where?

My recollection is that is_called is used to cover the boundary case where 
the 'current' value should not be incremented before being returned, but my 
memory is hazy. If this is the case, can we not just set it to true and set 
the value to (next - 1) unless (next - 1) < minv, in which case we set it 
to minv and set is_called to false?

Note that for the purpose of serial values we do not need to set the 
sequence exactly as it was internally, we just need to make sure that the 
next allocated value will be what we expect.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql Crash in -TIP
Next
From: Philip Warner
Date:
Subject: Why are triggers semi-deferred?