Re: Pg_dump
От | Tom Lane |
---|---|
Тема | Re: Pg_dump |
Дата | |
Msg-id | 1300348.1701975169@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Pg_dump (Holger Jakobs <holger@jakobs.com>) |
Ответы |
Re: Pg_dump
|
Список | pgsql-admin |
Holger Jakobs <holger@jakobs.com> writes: > Am 07.12.23 um 19:11 schrieb Rajesh Kumar: >> Will pg_dump cause blocking queries? If so how to take dump without >> blocking? > Readers don't block writers, writers don't block readers in PostgreSQL. > pg_dump is a reader. To enlarge on that a bit: pg_dump takes AccessShareLock on every table it intends to dump. This does not conflict with ordinary DML updates. It *will* conflict with anything that wants AccessExclusiveLock, which typically is schema-altering DDL. See https://www.postgresql.org/docs/current/explicit-locking.html#LOCKING-TABLES So the answer to your question is "don't try to alter the database schema while pg_dump is running". You can alter database content freely, though. regards, tom lane
В списке pgsql-admin по дате отправления: