Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAFGasm20737 for ; Thu, 15 Nov 2001 11:36:54 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) 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 fAFGaGc12805; Thu, 15 Nov 2001 11:36:16 -0500 (EST) To: Peter Eisentraut cc: Thomas Lockhart , Bruce Momjian , PostgreSQL Development Subject: Re: [DOCS] Use of 'now' In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Thu, 15 Nov 2001 17:15:48 +0100" Date: Thu, 15 Nov 2001 11:36:16 -0500 Message-ID: <12802.1005842176@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/524 X-Sequence-Number: 15379 Peter Eisentraut writes: > Thomas Lockhart writes: >> Previous versions of PostgreSQL can and will generate dump files which >> have 'current'. I did make it equivalent to 'now' for at least the 7.2 >> series of releases. > I don't think this is a good idea. If someone really relied on 'current' > for his application, substituting 'now' for it is not going to make things > better. If it's done silently it will definitely make things worse. I hadn't thought about it, but I believe Peter is right. Rejecting 'current' is better than silently translating it to 'now'. We have removed this feature and we shouldn't try to paper over the fact. regards, tom lane