| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> |
| 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 17:04:15 |
| Message-ID: | 2554675.1621184655@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2021-05-16 17:26:20 | Re: Removed extra memory allocations from create_list_bounds |
| Previous Message | Justin Pryzby | 2021-05-16 17:00:29 | Re: Removed extra memory allocations from create_list_bounds |