| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Arthur Zakirov <zaartur(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Allow to_date() and to_timestamp() to accept localized names |
| Date: | 2020-01-28 16:06:27 |
| Message-ID: | FAAEE111-67DF-4D61-84D8-44B67E1C72B3@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jan 28, 2020, at 7:47 AM, Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> wrote:
>
> This looks like a POSIX feature that some systems might not like (Windows [1]). But if this is something that the patch should aim to, I am fine with a RWF and give it another try in the future.
As long as this implementation doesn’t create a backward-compatibility problem when doing a more complete implementation later, I’m fine with this patch not tackling the whole problem.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-01-28 16:10:47 | Re: Is custom MemoryContext prohibited? |
| Previous Message | 曾文旌 (义从) | 2020-01-28 16:01:17 | Re: [Proposal] Global temporary tables |