| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Timezone abbreviations - out but not in? |
| Date: | 2008-06-10 16:01:27 |
| Message-ID: | 18632.1213113687@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> ... A more useful restriction would be to only output
> those that are in the set of input-acceptable abbreviations, but perhaps
> this is not easy to implement.
I think that is actually what Dave is suggesting, but I don't really
agree with it. To me it's a feature not a bug that timezone input
and output are decoupled. Would you have the input code refuse to
recognize abbrevs that are inconsistent with the current timezone
setting, even though the user intentionally set them up that way?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-10 16:03:06 | Re: Timezone abbreviations - out but not in? |
| Previous Message | Josh Berkus | 2008-06-10 16:01:05 | Re: Core team statement on replication in PostgreSQL |