Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection

From: Greg Sabino Mullane <htamfids(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: Re: UNLOGGED table CREATEd on one connection not immediately visible to another connection
Date: 2026-02-06 19:34:56
Message-ID: CAKAnmmKynqFFhvrEqqXv=yVGtip+kG6mkg3TZ7Z9DKO5JpNZ5w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 6, 2026 at 11:56 AM Geoff Winkless <pg(at)ukku(dot)uk> wrote:

> I'm fully prepared to accept that I'm doing something wrong because I've
> tried to reproduce the error using a couple of test PHP processes
> with a socket between them and haven't managed to reproduce the failure in
> several million tries, but I'm at a loss as to what to look
> for, so any suggestion would be gratefully accepted.
>

Temporarily set log_statement = 'all', then parse through the logs to find
the error, and look around it to see when the table was created.

Cheers,
Greg

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Junwang Zhao 2026-02-07 13:27:29 Re: Emitting JSON to file using COPY TO
Previous Message David G. Johnston 2026-02-06 17:34:13 UNLOGGED table CREATEd on one connection not immediately visible to another connection