From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Álvaro Herrera <alvherre@kurilemu.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: fix ancient typo in transformRelOptions()
Date: Wed, 6 Aug 2025 13:06:14 -0500
Message-ID: <aJOZlrQgGTskogtW@nathan> (raw)
In-Reply-To: <aJOMSPrvsr7fgl7C@nathan>
References: <202508052156.d7n5jjro3jne@alvherre.pgsql>
<1290107.1754431854@sss.pgh.pa.us>
<aJK72dWoPnTZrB63@nathan>
<aJOMSPrvsr7fgl7C@nathan>
On Wed, Aug 06, 2025 at 12:09:28PM -0500, Nathan Bossart wrote:
> On Tue, Aug 05, 2025 at 09:20:09PM -0500, Nathan Bossart wrote:
>> That explains it. I didn't find any past discussions about this particular
>> name, but commit de160e2 was being developed concurrently. I'll use
>> nameSpace instead.
>
> Committed.
Any thoughts on back-patching this? It's entirely cosmetic and could help
avoid some back-patching pain down the road. I originally chose not to
back-patch because it's not a bug and "namspace" has been there for a very
long time, but now I'm having second thoughts...
--
nathan
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: nathandbossart@gmail.com, tgl@sss.pgh.pa.us, alvherre@kurilemu.de
Subject: Re: fix ancient typo in transformRelOptions()
In-Reply-To: <aJOZlrQgGTskogtW@nathan>
* 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