From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Date/time types: big changeu |
Date: | 2000-02-18 15:52:48 |
Message-ID: | 552.950889168@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> Or were you talking about a server-side env variable?
> fwiw, we've already got that one...
We do? (... examines code ...) By golly, you're right.
OK, I agree with Peter: this is enough to save the day for a dbadmin
who really really doesn't want to switch to default ISO datestyle,
so I withdraw my complaint.
I do, however, suggest that the backend env var needs to be documented
more prominently than it is now. One might also ask why its set of
allowed values is inconsistent with the SET command's (probably
postgres.c ought to just call a routine in variable.c, rather than
having its own parsing code)?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-02-18 16:28:37 | Re: [HACKERS] Date/time types: big changeu |
Previous Message | Thomas Lockhart | 2000-02-18 15:48:29 | Re: [HACKERS] Date/time types: big changeu |