Lists: | pgsql-hackers |
---|
From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Can we drop ABSTIME? |
Date: | 2009-03-06 01:08:02 |
Message-ID: | 49B07772.9080208@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
All,
We've been carrying this warning in our docs since 7.4:
"The key word ABSTIME is ignored for historical reasons: In very old
releases of PostgreSQL, invalid values of type abstime were emitted as
Invalid Abstime. This is no longer the case however and this key word
will likely be dropped in a future release."
So given that it's been depreciated for 5 versions, maybe it's time to
rip it out?
--Josh
(thanks to rmxz for finding this)
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Can we drop ABSTIME? |
Date: | 2009-03-22 00:35:57 |
Message-ID: | 28515.1237682157@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> We've been carrying this warning in our docs since 7.4:
> "The key word ABSTIME is ignored for historical reasons: In very old
> releases of PostgreSQL, invalid values of type abstime were emitted as
> Invalid Abstime. This is no longer the case however and this key word
> will likely be dropped in a future release."
> So given that it's been depreciated for 5 versions, maybe it's time to
> rip it out?
Actually, the change in abstime's output function seems to have been
made in nabstime.c 1.14, committed Mar 14 1997 (pre-6.1). So I agree,
it's highly unlikely that anyone still needs this behavior.
regards, tom lane