| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Geoff Winkless <pg(at)ukku(dot)uk> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | UNLOGGED table CREATEd on one connection not immediately visible to another connection |
| Date: | 2026-02-06 17:34:13 |
| Message-ID: | CAKFQuwbuzBR3Z2qe+4SSeA+31Wo5LYQvgMy4TrAQF212BQs1Yg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday, February 6, 2026, Geoff Winkless <pg(at)ukku(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2026-02-06 19:34:56 | Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection |
| Previous Message | Geoff Winkless | 2026-02-06 16:55:49 | Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection |