Re: Enhancement to pg_dump
| От | Gregory Stark |
|---|---|
| Тема | Re: Enhancement to pg_dump |
| Дата | |
| Msg-id | 8763mar6qp.fsf@oxford.xeocode.com обсуждение исходный текст |
| Ответ на | Re: Enhancement to pg_dump (Rob Kirkbride <rob.kirkbride@gmail.com>) |
| Ответы |
Re: Enhancement to pg_dump
|
| Список | pgsql-hackers |
Rob Kirkbride <rob.kirkbride@gmail.com> writes: > Richard, > > Yes, I've changed it use TRUNCATE rather than DELETE and it's working well for > us now. I'm a bit surprised actually as it sounded like you were aiming to avoid the table lock. A TRUNCATE does require an exclusive lock on the table. It still has advantages over DROP in that there is no window when the table does not exist and any existing references to the table from views or functions will continue to function. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!
В списке pgsql-hackers по дате отправления: