X-Original-To: pgsql-general@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id AD5C4474E61; Sat, 15 Feb 2003 23:23:27 -0500 (EST) Received: from jester.inquent.com (CPE00508b028d7d-CM00803785c5e0.cpe.net.cable.rogers.com [24.103.51.175]) by postgresql.org (Postfix) with ESMTP id 052FA474E42; Sat, 15 Feb 2003 23:23:27 -0500 (EST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by jester.inquent.com (8.12.6/8.12.6) with ESMTP id h1G4O1Rf092311; Sat, 15 Feb 2003 23:24:01 -0500 (EST) (envelope-from rbt@rbt.ca) Subject: Re: is current_timestamp unique for a transaction? From: Rod Taylor To: Alan Gutierrez Cc: pgsql-sql@postgresql.org, PostgreSQL-general In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-nX7K1kbMR602l/KkOMj3" Organization: Message-Id: <1045369440.12011.54.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 15 Feb 2003 23:24:01 -0500 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/1052 X-Sequence-Number: 37806 --=-nX7K1kbMR602l/KkOMj3 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Not guaranteed, but also not likely to be the same value unless you have high volume. Use a sequence if you need a unique number. On Sat, 2003-02-15 at 22:49, Alan Gutierrez wrote: > Is current_timestamp(6) garunteed to be unique for each transaction? --=20 Rod Taylor PGP Key: http://www.rbt.ca/rbtpub.asc --=-nX7K1kbMR602l/KkOMj3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+TxJf6DETLow6vwwRAvLCAJ9/e40qtjVtGJ9hMNFj77aq2nnSLACfdetU ZABPtMhaPHNcGynSwouWsC4= =g+zk -----END PGP SIGNATURE----- --=-nX7K1kbMR602l/KkOMj3--