| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [DOCS] Use of 'now' |
| Date: | 2001-11-15 16:15:48 |
| Message-ID: | Pine.LNX.4.30.0111151535120.633-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luis Amigo | 2001-11-15 16:20:05 | bug?? on oid2name |
| Previous Message | Roland Roberts | 2001-11-15 15:57:53 | Re: [PATCHES] Interchange |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-11-15 16:16:07 | Re: Call for objections: revision of keyword classification |
| Previous Message | Peter Eisentraut | 2001-11-15 16:15:35 | Re: Open items |