pgsql: Avoid casting away const in sepgsql's quote_object_name.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Avoid casting away const in sepgsql's quote_object_name.
Date: 2022-08-27 16:52:59
Message-ID: E1oRz3K-000A9t-MP@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid casting away const in sepgsql's quote_object_name.

quote_identifier's API is designed on the assumption that it's
not worth worrying about a short-term memory leak when we have
to produce a quoted version of the given identifier. Whoever wrote
quote_object_name took it on themselves to override that judgment,
but the only way to do so is to cast away const someplace. We can
avoid that and substantially shorten the function by going along
with quote_identifier's opinion. AFAICS quote_object_name is not
used in any way where this would be unsustainable.

Per discussion of commit 45987aae2, which exposed that we had
a casting-away-const situation here.

Discussion: https://postgr.es/m/20220827112304.GL2342@telsasoft.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/94077df1c2def788f888a27ed0035236f806466d

Modified Files
--------------
contrib/sepgsql/label.c | 33 ++++++---------------------------
1 file changed, 6 insertions(+), 27 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-08-28 07:21:47 pgsql: Enable RandomizedBaseAddress (ASLR) on Windows with MSVC builds
Previous Message Tom Lane 2022-08-27 16:16:32 pgsql: Doc: add comment about bug fixed in back branches as of 3f7323cb