From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ERROR: could not open relation with OID XXXX |
Date: | 2024-08-25 14:31:02 |
Message-ID: | CANzqJaArn7Ubn6U_Ny9CSUpEjJ3rN5erE92g7fo_aO9cm8Fpwg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 25, 2024 at 9:42 AM Marcelo Zabani <mzabani(at)gmail(dot)com> wrote:
> Hi all,
>
> I can reproduce the error in the subject from time to time when querying
> catalog tables while DDL is happening concurrently. Here's a bash script
> that reproduces it (not always, you might have to run it many times until
> you see ERROR: could not open relation with OID XXXX):
>
[snip]
> I've seen this happen in Production without pg_sleep in the mix, too. I
> added pg_sleep to the example above only because it makes the error easier
> to reproduce.
>
What version (including minor number)?
> Is there something I can do to avoid this? Is my understanding of how the
> catalog tables work wrong?
>
Just out of curiosity, *WHY* do you do this? It's never occurred to me to
do that; maybe it's something useful that I've been overlooking.
--
Death to America, and butter sauce.
Iraq lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Marcelo Zabani | 2024-08-25 15:05:22 | Re: ERROR: could not open relation with OID XXXX |
Previous Message | Marcelo Zabani | 2024-08-25 13:42:33 | ERROR: could not open relation with OID XXXX |