mirror of
https://github.com/postgres/postgres.git
synced 2026-04-10 03:26:23 -04:00
6faca9ae28
If temp tables have dependencies (such as sequences) then it's possible for autovacuum's cleanup of orphan temp tables to deadlock against an incoming backend that's trying to clean out the temp namespace for its own use. That can happen because RemoveTempRelations' performDeletion call can visit objects within the namespace in an order different from the order in which a per-table deletion will visit them. To fix, observe that performDeletion will begin by taking an exclusive lock on the temp namespace (even though it won't actually delete it). So, if we can get a shared lock on the namespace, we can be sure we're not running concurrently with RemoveTempRelations, while also not conflicting with ordinary use of the namespace. This requires introducing a conditional version of LockDatabaseObject, but that's no big deal. (It's surprising we've got along without that this long.) Report and patch by Mikhail Zhilin. Back-patch to all supported branches. Discussion: https://postgr.es/m/c43ce028-2bc2-4865-9b89-3f706246eed5@postgrespro.ru |
||
|---|---|---|
| .. | ||
| autovacuum.c | ||
| auxprocess.c | ||
| bgworker.c | ||
| bgwriter.c | ||
| checkpointer.c | ||
| fork_process.c | ||
| interrupt.c | ||
| launch_backend.c | ||
| Makefile | ||
| meson.build | ||
| pgarch.c | ||
| postmaster.c | ||
| startup.c | ||
| syslogger.c | ||
| walsummarizer.c | ||
| walwriter.c | ||