Re: PoC: Simplify recovery after dropping a table by LOGGING the restore LSN

Andrey Borodin <x4mmm@yandex-team.ru>

From: Andrey Borodin <x4mmm@yandex-team.ru>

To: Дмитрий Лебедев <idemonlebedev@gmail.com>

Cc: Kirill Reshke <reshkekirill@gmail.com>, Kirk Wolak <wolakk@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Nikolay Samokhvalov <samokhvalov@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Pavel Stehule <pavel.stehule@gmail.com>

Date: 2025-12-10T09:53:02Z

Lists: pgsql-hackers

Attachments

v5-0001-Add-log_object_drops-GUC-for-DROP-TABLE-DATABASE-.patch (application/octet-stream)

> On 1 Dec 2025, at 12:11, Дмитрий Лебедев <idemonlebedev@gmail.com> wrote:
> 
> I've implemented an improved version of this feature that addresses 
> Kirill's concern about logging the wrong LSN [1].

Cool! On a first glance patch looks good. I'll test it more later, for now I've fixed indentation and rebased on master to fix conflicts with recent "wait for LSN feature".

Please also avoid top posting :) Post answers below cited text. And do not post unrelevant citations at all. Mail archives a read more frequently than written.

Also, it's a good idea to number patch versions so reviewers can post feedback for some specific version. Here I used version number 5.

Thanks!

Best regards, Andrey Borodin.