From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200310220431.h9M4VXl20009@candle.pha.pa.us>
Subject: Re: 7.4 compatibility question
In-Reply-To: <8468.1066796494@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 22 Oct 2003 00:31:33 -0400 (EDT)
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	Hackers <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
> Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> >>> Now that DEFAULT 'now' will not work in PostgreSQL 7.4,  will DEFAULT 
> >>> 'infinity' and DEFAULT '-infinity' and the like stop working as well? 
> >> 
> >> No, because those values don't change over time.  The issue here is when
> >> exactly does the default value get evaluated...
> 
> > Ah, of course - but what about 'yesterday' and 'tomorrow' - these should 
> > also be mentioned in the release notes.
> 
> Good point ... not that I think anyone is actually using such a default
> in the field, but the behavior did change ...

It would be pretty strange to use those as a default --- I am not
inclined to mention it in the release notes --- we don't mention every
change, only significant ones.

-- 
  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