Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 642A7475957 for ; Wed, 27 Feb 2002 00:48:13 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g1R5m4S20077; Wed, 27 Feb 2002 00:48:04 -0500 (EST) To: "Christopher Kings-Lynne" Cc: "Matteo Beccati" , pgsql-sql@postgresql.org Subject: Re: Timestamp output In-reply-to: References: Comments: In-reply-to "Christopher Kings-Lynne" message dated "Wed, 27 Feb 2002 11:17:05 +0800" Date: Wed, 27 Feb 2002 00:48:04 -0500 Message-ID: <20074.1014788884@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/416 X-Sequence-Number: 6838 "Christopher Kings-Lynne" writes: > Hmmm...it seems to me that an easier way is to edit the pg_dump from the > previous version to add (0) in everywhere. Well, sure, if you haven't loaded your dump yet. Note, however, that this does *not* provide a closer approximation to the behavior of older versions than 7.2 does by default. Older versions do support fractional-second timestamps, though only to a couple of digits IIRC. The main thing that would be useful to avoid breaking client code that can't handle fractional-second timestamps is to replace calls to now() and current_timestamp with current_timestamp(0). regards, tom lane