Re: Tightening up allowed custom GUC names - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Tightening up allowed custom GUC names
Date
Msg-id 1477413.1613068373@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tightening up allowed custom GUC names  (Noah Misch <noah@leadboat.com>)
Responses Re: Tightening up allowed custom GUC names
Re: Tightening up allowed custom GUC names
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Tue, Feb 09, 2021 at 05:34:37PM -0500, Tom Lane wrote:
>> * A case could be made for tightening things up a lot more, and not
>> allowing anything that doesn't look like an identifier.  I'm not
>> pushing for that, as it seems more likely to break existing
>> applications than the narrow restriction proposed here.  But I could
>> live with it if people prefer that way.

> I'd prefer that.  Characters like backslash, space, and double quote have
> significant potential to reveal bugs, while having negligible application
> beyond revealing bugs.

Any other opinions here?  I'm hesitant to make such a change on the
basis of just one vote.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Joshua Drake
Date:
Subject: Re: Extensibility of the PostgreSQL wire protocol
Next
From: Tom Lane
Date:
Subject: Re: Detecting pointer misalignment (was Re: pgsql: Implementation of subscripting for jsonb)