Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 58782475EB9; Tue, 24 Sep 2002 17:57:03 -0400 (EDT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 771DE47608D; Tue, 24 Sep 2002 17:57:01 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g8OLuq815295; Tue, 24 Sep 2002 17:56:52 -0400 (EDT) From: Bruce Momjian Message-Id: <200209242156.g8OLuq815295@candle.pha.pa.us> Subject: Re: [SQL] CURRENT_TIMESTAMP In-Reply-To: To: Roland Roberts Date: Tue, 24 Sep 2002 17:56:51 -0400 (EDT) Cc: pgsql-sql@postgresql.org, pgsql-general@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/1086 X-Sequence-Number: 30667 Roland Roberts wrote: > >>>>> "Ross" == Ross J Reedstrom writes: > > Ross> Oh, interesting datapoint. Let me get this clear - on > Ross> oracle, the equivalent of: > > Well, I've never gone off to lunch in the middle, but in Oracle 7, I > had transactions which definitely took as much as a few minutes to > complete where the timestamp on every row committed was the same. Can you run a test: BEGIN; SELECT CURRENT_TIMESTAMP; wait 5 seconds SELECT CURRENT_TIMESTAMP; Are the two times the same? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073