Re: making the backend's json parser work in frontend code
| От | Alvaro Herrera |
|---|---|
| Тема | Re: making the backend's json parser work in frontend code |
| Дата | |
| Msg-id | 20200124170001.GA10552@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: making the backend's json parser work in frontend code (David Steele <david@pgmasters.net>) |
| Ответы |
Re: making the backend's json parser work in frontend code
|
| Список | 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
В списке pgsql-hackers по дате отправления: