Re: Autovacuum breakage from a734fd5d1 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Autovacuum breakage from a734fd5d1
Date
Msg-id 3784.1480301213@sss.pgh.pa.us
Whole thread Raw
In response to Re: Autovacuum breakage from a734fd5d1  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Autovacuum breakage from a734fd5d1  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> In order to reproduce the failure I have just inserted a manual
> pg_usleep before looping through the list of orphan_oids, and after
> dropping manually from another session a couple of orphaned temporary
> tables I was able to see the failure. Attached is a proposal of patch.

That's not really adequate, because acquiring the lock doesn't prove that
the table still exists; you might just be holding a useless lock against
a now-unused OID.  You really need to do something to verify that the
table's catalog entries are still visible after you have the lock.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Parallel bitmap heap scan
Next
From: Michael Paquier
Date:
Subject: Re: Fixed pg_class refcache leak when the meta tuple in pg_class in invalid.