Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1siEH2-000nH0-El for pgsql-general@arkaria.postgresql.org; Sun, 25 Aug 2024 14:31:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1siEH0-00FgrQ-HI for pgsql-general@arkaria.postgresql.org; Sun, 25 Aug 2024 14:31:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1siEH0-00FgrH-5a for pgsql-general@lists.postgresql.org; Sun, 25 Aug 2024 14:31:18 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1siEGx-001N93-UD for pgsql-general@lists.postgresql.org; Sun, 25 Aug 2024 14:31:17 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5d5bb03fe42so2475782eaf.3 for ; Sun, 25 Aug 2024 07:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724596274; x=1725201074; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=X3ZRcgH4IHvLdwDgMz5/TqfzjXAmegLKsWxoeN9P3ts=; b=SCVitvg8/x9pDuhqAnkfdUIz4I0I+GM4OnrIyiAJDV7q/rkTWtTSWD4uqV6QloqzUE zbaXYEvT8J+dVVLAcrq4+GWTtkuGYOgN69REoEBEKSkMYc9G2Se2sANlSbEwlaeF04fE PrlaG2LKElSNYT8y+gNDAzje+8H5jjnpAEntuYEgytR5aLOzDNxtUWNDS+uqovbP3Uf+ XLdAyNja4DBXZ94TFI360vCfz6D6dgGB7uwo9m0+qc2+COTtlksd/mB4oi0soqaU9jWH WiQ7Q6dmc5oXgzjxwPYrgYqdSQkUo8MvQxcYu216ge493XGeQhlyvdTjTqjKur6cooPr P3jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724596274; x=1725201074; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=X3ZRcgH4IHvLdwDgMz5/TqfzjXAmegLKsWxoeN9P3ts=; b=VJrGUsY+5a1BasKgZ0n17M8Bs6pC5U1PRIj3dDWPoU6LR0DQEBMfTcmkwojg/SyOpV i0ElsEMUhAF6CGHzLCZ2HCmZCkILhbxcUXr806woB7PYQMjHRLPjmYdixZbr4Bamc5MY 5kQVeRHq0rpGG4wiFygK1mUElveUAgNy9Y7ljfMpEl3P1+4srppCia+eE7HRSY8Cj/b6 gL1YNd3k9Qm1Oy4kCxXwfn74a6FVY+KQGUxyyrWTufaZX+9ge7+BO78B/uU30+O9zkwU RN2mjYmmp/NWdaLOTAEmnpoYgeWksfcRDP0/kJxC+uEoK/x5ysMpsQgdltUQc8BDCxuT 6JRQ== X-Gm-Message-State: AOJu0Yw4Acdvfu9tddbAxIE4rM7xCvc1t0kZ0+kpniBTVTdGg94P/Tet 2qWrdWkjH2k9jDVuPTAZI7nX6gxunAkXpy3gCdiAmnhfqJF53Blnvhv/HGKLvbp904BVHuRfHa5 9JIE3lyoWx1IBV/tTIhlWt5H7Ou3R8w== X-Google-Smtp-Source: AGHT+IF/F6e/UR9sj36HaEACP5epCDC4hw8UgTSHx4MtY6T39DNz0dPaPJS2X0WsJzWTOD+dLGSRHhCkuHxpcRm19Rk= X-Received: by 2002:a05:6820:174a:b0:5d5:b49c:b6f7 with SMTP id 006d021491bc7-5dcc6285224mr8188510eaf.7.1724596273802; Sun, 25 Aug 2024 07:31:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sun, 25 Aug 2024 10:31:02 -0400 Message-ID: Subject: Re: ERROR: could not open relation with OID XXXX To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000047f8df062082dccd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000047f8df062082dccd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Aug 25, 2024 at 9:42=E2=80=AFAM Marcelo Zabani = 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 easie= r > 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. --=20 Death to America, and butter sauce. Iraq lobster! --00000000000047f8df062082dccd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

--
Death to America, and butter sauce.
Iraq lobster!
--00000000000047f8df062082dccd--