X-Original-To: pgsql-general@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5D95C47580B for ; Sat, 15 Feb 2003 23:15:18 -0500 (EST) Received: from wolff.to (wolff.to [66.93.249.74]) by postgresql.org (Postfix) with SMTP id C8192474E42 for ; Sat, 15 Feb 2003 23:15:17 -0500 (EST) Received: (qmail 2378 invoked by uid 500); 16 Feb 2003 04:28:51 -0000 Date: Sat, 15 Feb 2003 22:28:51 -0600 From: Bruno Wolff III To: Alan Gutierrez Cc: pgsql-sql@postgresql.org, PostgreSQL-general Subject: Re: [SQL] is current_timestamp unique for a transaction? Message-ID: <20030216042851.GA2273@wolff.to> Mail-Followup-To: Alan Gutierrez , pgsql-sql@postgresql.org, PostgreSQL-general References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/923 X-Sequence-Number: 37677 On Sat, Feb 15, 2003 at 21:49:34 -0600, Alan Gutierrez wrote: > > Is current_timestamp(6) garunteed to be unique for each transaction? No. If you want guarenteed uniqueness use a sequence.