Re: Is this a problem in GenericXLogFinish()?
| От | Jeff Davis |
|---|---|
| Тема | Re: Is this a problem in GenericXLogFinish()? |
| Дата | |
| Msg-id | 4b2dfe9c67713413a06be761f677bc34222afcb4.camel@j-davis.com обсуждение исходный текст |
| Ответ на | Re: Is this a problem in GenericXLogFinish()? (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Is this a problem in GenericXLogFinish()?
|
| Список | pgsql-hackers |
On Thu, 2023-10-19 at 16:12 -0400, Robert Haas wrote:
> For what it's worth, though, I think it would be better to
> just make these cases exceptions to your Assert
OK, I'll probably commit something like v4 then.
I still have a question though: if a buffer is exclusive-locked,
unmodified and clean, and then the caller registers it and later does
PageSetLSN (just as if it were dirty), is that a definite bug?
There are a couple callsites where the control flow is complex enough
that it's hard to be sure the buffer is always marked dirty before
being registered (like in log_heap_visible(), as I mentioned upthread).
But those callsites are all doing PageSetLSN, unlike the hash index
case.
Regards,
Jeff Davis
В списке pgsql-hackers по дате отправления: