From: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Query about time zone patterns in to_char |
Date: | 2021-05-16 18:22:41 |
Message-ID: | CAMm1aWZOKoVdSqvVxZJZ2ADjDkUEZ7fm-+DW2rGqnS-FJMXQYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hm. If Oracle does that, then there's an argument for us doing it
> too. I can't get hugely excited about it, but maybe someone else
> cares enough to prepare a patch.
Thanks for the confirmation. Attached patch supports these format
patterns. Kindly review and let me know if any changes are required.
Thanks & Regards,
Nitin Jadhav
On Sun, May 16, 2021 at 10:34 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> writes:
> > Thanks for the explanation. I also feel that we may not support every
> > case-variant. But the other reason which triggered me to think in the
> > other way is, as mentioned in commit [1] where this feature was added,
> > says that these format patterns are compatible with Oracle. Whereas
> > Oracle supports both upper case and lower case patterns. I just wanted
> > to get it confirmed with this point before concluding.
>
> Hm. If Oracle does that, then there's an argument for us doing it
> too. I can't get hugely excited about it, but maybe someone else
> cares enough to prepare a patch.
>
> regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
v1_support_of_tzh_tzm_patters.patch | application/octet-stream | 5.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-05-16 20:23:02 | Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 |
Previous Message | Zhihong Yu | 2021-05-16 17:26:20 | Re: Removed extra memory allocations from create_list_bounds |