| From: | Salma Elsayed <salmasayed182003(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | Kirk Wolak <wolakk(at)gmail(dot)com>, zsolt(dot)parragi(at)percona(dot)com, Kirill Reshke <reshkekirill(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: PoC: Simplify recovery after dropping a table by LOGGING the restore LSN |
| Date: | 2026-10-28 20:17:37 |
| Message-ID: | CANBEAPFksvg8Yy2kD3bun4uhOz=w-rNFDxev1ibZJz_3EtHQhg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, Oct 21, 2026 at 4:50 PM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
>
> I agree that leaving drop database for another patch is a good idea.
> Having it would be quite nice, bit it's indeed much harder than we
> anticipated, so I guess it's ok to postpone it.
>
Attached is v11, which removes DROP DATABASE as discussed, applies the
error style guide to the log messages, and simplifies the TAP test.
Best,
Salma Elsayed
| Attachment | Content-Type | Size |
|---|---|---|
| v11-0001-Add-LSN-logging-for-DROP-TABLE-and-TRUNCATE-TABL.patch | text/x-patch | 30.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dongpo Liu | 2026-10-28 20:26:02 | Re: Wrong results from an antijoin |
| Previous Message | Robert Haas | 2026-10-28 19:32:44 | Re: pgsql: Set HEAP_XMAX_INVALID for tuples updated by aborted subtransacti |