| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: fix ancient typo in transformRelOptions() |
| Date: | 2025-08-06 18:08:40 |
| Message-ID: | 1db4dd40-2bbf-4a44-abe8-1e5c793ae4fc@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06.08.25 20:06, Nathan Bossart wrote:
> 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...
I'd leave it alone for now. We could still choose to backpatch this one
if we end up backpatching something that goes on top of it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-08-06 18:14:12 | Re: analyze-in-stages post upgrade questions |
| Previous Message | Álvaro Herrera | 2025-08-06 18:06:22 | Re: Partition-wise join with whole row vars |