| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Tracking timezone abbreviation removals in the IANA tz database |
| Date: | 2016-09-02 16:30:16 |
| Message-ID: | 18037.1472833816@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> So the idea I'm toying with (again, haven't tried to code this) is to say
> that *if* we can match the abbreviation to something in the referenced
> zone then we'll use that, but otherwise we fall back to treating the
> abbreviation as a macro for the zone name.
This turned out to require only fairly localized code changes. So
I now propose that we leave the tznames files as-is and apply the
attached patch (plus documentation changes, which I've not done yet).
Any objections?
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| allow-timezone-abbrevs-not-matching-iana-data.patch | text/x-diff | 7.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-09-02 16:31:50 | Re: amcheck (B-Tree integrity checking tool) |
| Previous Message | Andres Freund | 2016-09-02 16:25:53 | Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling) |