Re: Postgres perl module namespace

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Erik Rijkers <er(at)xs4all(dot)nl>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres perl module namespace
Date: 2022-04-18 14:44:29
Message-ID: 20220418144429.si5dmslz2ek3mi7s@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-04-18 10:26:15 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I just, again, tried to backport a test as part of a bugfix. The
> > renaming between 14 and 15 makes that task almost comically harder. The
> > only way I see of dealing with that for the next 5 years is to just
> > never backpatch tests to < 15. Which seems like a bad outcome.
>
> Yeah ...
>
> > Except that it's *way* too late I would argue that this should just
> > straight up be reverted until that aspect is addressed. It's a
> > maintenance nightmare.
>
> I'm not for that

I'm not either, at this point...

> but could it be sane to back-patch the renaming?

That might be the best. But it might not even suffice. There've been
other global refactorings between 14 and 15. E.g. 201a76183e2.

I wonder if we should just backpatch the current PostgreSQL module, but
leave the old stuff around :/.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-04-18 14:50:03 Re: Crash in new pgstats code
Previous Message Robert Haas 2022-04-18 14:44:22 Re: TRAP: FailedAssertion("HaveRegisteredOrActiveSnapshot()", File: "toast_internals.c", Line: 670, PID: 19403)