Thread: Re: [DOCS] Use of 'now'

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.

If that someone replays his dump and sees "invalid date/time value
'current'" then he knows he's got something to fix -- and he has to fix
something anyway.

-- 
Peter Eisentraut   peter_e@gmx.net

Peter Eisentraut <peter_e@gmx.net> 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