pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Milen A. Radev <milen@radev.net>
To: pgsql-sql@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: system table storing sequence attributes
Date: Tue, 22 May 2007 17:01:15 +0300
Message-ID: <4652F7AB.9040502@radev.net> (raw)
In-Reply-To: <f2uq6o$112t$1@news.hub.org>
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>

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




view thread (9+ messages)

Message-ID: <4652F7AB.9040502@radev.net>
Permalink:  ../4652F7AB.9040502@radev.net/
Also on:    postgresql.org/message-id/4652F7AB.9040502@radev.net

 · 

reply

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-sql@postgresql.org
  Cc: milen@radev.net
  Subject: Re: system table storing sequence attributes
  In-Reply-To: <4652F7AB.9040502@radev.net>

* 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