Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
| От | Tom Lane |
|---|---|
| Тема | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
| Дата | |
| Msg-id | 3681809.1659654848@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints (Dilip Kumar <dilipbalaut@gmail.com>) |
| Ответы |
Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
|
| Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes:
> On 2022-08-04 18:05:25 -0400, Tom Lane wrote:
>> In any case, DROP DATABASE is far from the only place with a problem.
> What other place has a database corrupting potential of this magnitude just
> because interrupts are accepted? We throw valid s_b contents away and then
> accept interrupts before committing - with predictable results. We also accept
> interrupts as part of deleting the db data dir (due to catalog access).
Those things would be better handled by moving the data-discarding
steps to post-commit. Maybe that argues for having an internal
commit halfway through DROP DATABASE: remove pg_database row,
commit, start new transaction, clean up.
regards, tom lane
В списке pgsql-hackers по дате отправления: