Re: pgsql: Perform provider-specific initialization in new functions.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Perform provider-specific initialization in new functions.
Date: 2026-04-22 19:24:45
Message-ID: 97199d95e7fc74fc169fdce410942f854cd774b6.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, 2026-04-21 at 21:48 -0700, Jeff Davis wrote:
> I attached a new patch, and only the commit message is different,
> which
> I plan to backport to 17.

Committed.

> There's another bug, though. Even with the patch applied, if you do
> the
> same pg_receivewal command immediately after starting the server
> (without any other connections), you get:
>
>   FATAL:  cannot read pg_class without having selected a database

This is a separate issue so I moved the discussion here:

https://www.postgresql.org/message-id/d8f8e11f06d692fff89e6be0f22732d30cf695a0.camel@j-davis.com

Any other loose ends from this discussion?

Regards,
Jeff Davis

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2026-04-23 04:49:49 pgsql: Fix new-to-v19 -Wshadow warnings
Previous Message Jeff Davis 2026-04-22 17:27:41 pgsql: catcache.c: use C_COLLATION_OID for texteqfast/texthashfast.