| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Bhuvan A <bhuvansql(at)yahoo(dot)com> |
| Cc: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Sequencing Problem in Transaction.. |
| Date: | 2002-02-12 06:21:42 |
| Message-ID: | 20020211221922.S88298-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Tue, 12 Feb 2002, Bhuvan A wrote:
>
> Dear All,
>
> In postgresql 7.1, there is a problem in sequence.
>
> While rollbacking in transaction mode, the sequences are not actually
> getting rolled back. This problem is still there in 7.2, it seems!
>
Probably never, this is the intented behavior. If rollbacks rolled the
sequences back then you'd have to wait for the first transaction to
rollback or commit before giving the number out to a second transaction
running at the same time (thus you'd effectively be limited to a single
concurrent inserting transaction for most uses of sequences)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Unnikrishnan Menon | 2002-02-12 06:56:06 | Re: Oracle "Jobs" in PostgreSQL |
| Previous Message | Christopher Kings-Lynne | 2002-02-12 06:04:49 | Re: Storing text data in databases. |