To: pgsql-sql@postgresql.org
From: "Milen A. Radev" <milen@radev.net>
Subject: Re: system table storing sequence attributes
Date: Tue, 22 May 2007 17:01:15 +0300
Lines: 21
Message-ID: <4652F7AB.9040502@radev.net>
References: <f2u4jn$a03$1@news.hub.org>
	<pan.2007.05.22.07.43.23.678145@gmail.com>
	<f2unc1$kdo$1@news.hub.org>
	<pan.2007.05.22.12.41.38.862364@gmail.com>
	<f2uq6o$112t$1@news.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: pgsql-sql@postgresql.org
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
In-Reply-To: <f2uq6o$112t$1@news.hub.org>

Sabin Coanda написа:
> ""Marcin Stкpnicki"" <mstepnicki@gmail.com> wrote in message 
> news:pan.2007.05.22.12.41.38.862364@gmail.com...
> ...
>> I think that you either misunderstood this statement or try to break your
>> application in a nasty way ;). Please tell us more about your problem
>> and/or what do you want to achive, because sequences behave this way for a
>> reason (concurrency issues). Perhaps there is another solution.
> 
> I have a table with a serial primary key aoto generated by a sequence. I 
> add/remove records. At a moment I'd like to know what is the current value 
> of the sequence. I don't wish to know this in the same session where I 
> add/remove records.

Why do you need to know that? I can't think of any reason.

[...]


-- 
Milen A. Radev