| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: making the backend's json parser work in frontend code |
| Date: | 2020-01-24 17:00:01 |
| Message-ID: | 20200124170001.GA10552@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jan-24, David Steele wrote:
> It might be nice to have a strict mode where non-ASCII/UTF8 characters will
> error instead, but that can be added on later.
"your backup failed because you have a file we don't like" is not great
behavior. IIRC we already fail when a file is owned by root (or maybe
unreadable and owned by root), and it messes up severely when people
edit postgresql.conf as root. Let's not add more cases of that sort.
Maybe we can get away with *ignoring* such files, perhaps after emitting
a warning.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2020-01-24 17:03:22 | Re: Duplicate Workers entries in some EXPLAIN plans |
| Previous Message | Tom Lane | 2020-01-24 16:46:48 | Re: Allow to_date() and to_timestamp() to accept localized names |