Re: BUG #14063: ALTER SYSTEM accepts 'newline' and renders itself inoperable.
От | Tom Lane |
---|---|
Тема | Re: BUG #14063: ALTER SYSTEM accepts 'newline' and renders itself inoperable. |
Дата | |
Msg-id | 14245.1459806043@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | BUG #14063: ALTER SYSTEM accepts 'newline' and renders itself inoperable. (julian.schauder@credativ.de) |
Список | pgsql-bugs |
julian.schauder@credativ.de writes: > PostgreSQLs ALTER SYSTEM accepts a newline in its string-statements. This > will cause the postgresql.auto.conf to become unreadable and requires system > intervention (aka removal of the auto.conf) Yeah, there's no provision for allowing a newline in postgresql.conf string literals. I believe we debated this in the past and decided it wasn't something we wanted to change, as it would create more confusion than it was worth (for example: what line number to ascribe to such an assignment). It looks like newline is the only troublesome character; there are quoting conventions for backslash and quote, which are the only other characters that are special there. > According to code analysis i believe the easiest way around this is > tightening the value validation and ignore whitespaces or just remove > newline as a whitespace. I'm inclined to just throw an error if someone tries this, not try to clean up after them. If we get lots of complaints about it, we will know we should revisit the aforementioned decision. But there's no reason to put restrictions on GUC values that aren't getting written by ALTER SYSTEM. regards, tom lane
В списке pgsql-bugs по дате отправления: