Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1C6LhE40467 for ; Tue, 12 Feb 2002 01:21:47 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id AAA00D5FB; Mon, 11 Feb 2002 22:21:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id A04F55BF8; Mon, 11 Feb 2002 22:21:42 -0800 (PST) Date: Mon, 11 Feb 2002 22:21:42 -0800 (PST) From: Stephan Szabo To: Bhuvan A Cc: Subject: Re: Sequencing Problem in Transaction.. In-Reply-To: Message-ID: <20020211221922.S88298-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200202/128 X-Sequence-Number: 6556 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)