Re: timestamp bug 7.4beta3 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: timestamp bug 7.4beta3
Date
Msg-id 17692.1066247071@sss.pgh.pa.us
Whole thread Raw
In response to Re: timestamp bug 7.4beta3  (Neil Conway <neilc@samurai.com>)
List pgsql-bugs
Neil Conway <neilc@samurai.com> writes:
> I agree that this kind of silent backward-incompatibility isn't good,

It's unpleasant, but we were going to have to bite this bullet sooner or
later.  Allowing 'now' to work like a non-constant in this context was
always a fragile hack.

> Tom, can we improve the upgrade experience in this case?

I don't see any very simple way; certainly not anything I'd want to
stick in in a last-minute fashion.  There are too many possible
representations of 'now', and if we did try to substitute now() we'd
be disabling a legal (if possibly useless) behavior.

It's not like it's hard to fix post-upgrade (or pre-upgrade, for that
matter): a simple "ALTER TABLE ... SET DEFAULT now()" will do it.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Neil Conway
Date:
Subject: Re: timestamp bug 7.4beta3
Next
From: "Nayib Kiuhan"
Date:
Subject: Re: timestamp bug 7.4beta3