From: | "Milen A(dot) Radev" <milen(at)radev(dot)net> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: system table storing sequence attributes |
Date: | 2007-05-22 14:01:15 |
Message-ID: | 4652F7AB.9040502@radev.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Sabin Coanda написа:
> ""Marcin Stкpnicki"" <mstepnicki(at)gmail(dot)com> wrote in message
> news:pan(dot)2007(dot)05(dot)22(dot)12(dot)41(dot)38(dot)862364(at)gmail(dot)com(dot)(dot)(dot)
> ...
>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | John Summerfield | 2007-05-23 13:41:00 | FATAL: cache lookup failed for function 1003 |
Previous Message | Sabin Coanda | 2007-05-22 13:47:03 | Re: system table storing sequence attributes |