BUG #15775: pg_get_indexdef: could not open relation with OID 16385

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: ptang(at)pivotal(dot)io
Subject: BUG #15775: pg_get_indexdef: could not open relation with OID 16385
Date: 2019-04-23 03:19:21
Message-ID: 15775-beb18bcc52db9e36@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15775
Logged by: Pengzhou Tang
Email address: ptang(at)pivotal(dot)io
PostgreSQL version: 11.2
Operating system: centos 7
Description:

Hi, Developers,

I hit this error when running bellow queries concurrently:
1. select pg_get_indexdef('idx_foo'::regclass);
2. drop table foo;

To repo easier, break at set_relation_column_names in session 1 and then run
session 2, error occurs.

Question:
Why pg_get_expr() doesn't acquire and hold an AccessShareLock if it needs to
access the relation later.

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-04-23 06:57:01 Re: Possible to store invalid SCRAM-SHA-256 Passwords
Previous Message Michael Paquier 2019-04-23 02:10:18 Re: Possible to store invalid SCRAM-SHA-256 Passwords