UNLOGGED table CREATEd on one connection not immediately visible to another connection - Mailing list pgsql-general

From David G. Johnston
Subject UNLOGGED table CREATEd on one connection not immediately visible to another connection
Date
Msg-id CAKFQuwbuzBR3Z2qe+4SSeA+31Wo5LYQvgMy4TrAQF212BQs1Yg@mail.gmail.com
Whole thread
In response to Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection  (Geoff Winkless <pg@ukku.uk>)
List pgsql-general
On Friday, February 6, 2026, Geoff Winkless <pg@ukku.uk> wrote:

I can't provide the entire code, because it's not open. It's using
libpq and our own wrapper around PQsendQuery that handles things like
autoretries, auto-reconnection and grabbing all results to ensure the
connection is kept in a consistent state.

Have you investigated schema and search_path interactions?

Do you have a reproducer on your end, can try different versions of PostgreSQL to see if it is a regression?  Or to then remove components to isolate a middleware dynamic.  We’d probably need a reproducer without any customizations to begin debugging core.

What version are you on?

David J.

pgsql-general by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection
Next
From: Greg Sabino Mullane
Date:
Subject: Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection