Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work
| От | Tom Lane |
|---|---|
| Тема | Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work |
| Дата | |
| Msg-id | 767221.1660015637@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work
|
| Список | pgsql-hackers |
I wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
>> The only hunk I'm having second thoughts about is the following, which
>> makes unexpected stray files break checkpoints:
> Sounds like a pretty bad idea. What's the upside?
Actually, having now read the patch, I don't think there is any
part of 0002 that is a good idea. It's blithely removing the
comments that explain why the existing coding is the way it is,
and not providing a shred of justification for making checkpoints
more brittle.
I have not tried to analyze the error-handling properties of 0001,
but if it's being equally cavalier then it shouldn't be committed
either. Most of this behavior is the result of decades of hard-won
experience; discarding it because it doesn't fit conveniently
into some refactoring plan isn't smart.
regards, tom lane
В списке pgsql-hackers по дате отправления: