From: Chapman Flack <jcflack@acm.org>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: tighten generic_option_name, or store more carefully in catalog?
Date: Fri, 23 May 2025 17:40:00 -0400
Message-ID: <6830EB30.8090904@acm.org> (raw)
Hi,
generic_option_name is a ColLabel, therefore a fully general SQL identifier.
But a command like CREATE FOREIGN DATA WRAPPER w ... OPTIONS ("a=b" 'c=d')
stores {a=b=c=d} in fdwoptions, from which the original intent can't be
recovered.
Should generic_option_name be restricted to be a regular identifier,
or allowed to be a delimited identifier but with = forbidden within it,
or should it be represented as delimited in the catalog when necessary
so it can be recovered faithfully?
SQL rules would also make its case-sensitivity dependent on faithfully
recovering whether it was delimited or not.
Regards,
-Chap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jcflack@acm.org
Subject: Re: tighten generic_option_name, or store more carefully in catalog?
In-Reply-To: <6830EB30.8090904@acm.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox