Re: POC: Cleaning up orphaned files using undo logs

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: POC: Cleaning up orphaned files using undo logs
Date: 2022-01-12 08:27:26
Message-ID: CAOBaU_ZMKVs_1jadL-JKbtafiC89yc0x+3ToDyQavHvLqrucjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Nov 25, 2021 at 10:00 PM Antonin Houska <ah(at)cybertec(dot)at> wrote:
>
> So it should be ok if the temporary undo is managed and discarded by
> individual backends. Patch 0005 of the new series tries to do that.

The cfbot reports that at least the 001 patch doesn't apply anymore:
http://cfbot.cputube.org/patch_36_3228.log
> === applying patch ./undo-20211125/0001-Add-SmgrId-to-smgropen-and-BufferTag.patch
> [...]
> patching file src/bin/pg_waldump/pg_waldump.c
> Hunk #1 succeeded at 480 (offset 17 lines).
> Hunk #2 FAILED at 500.
> Hunk #3 FAILED at 531.
> 2 out of 3 hunks FAILED -- saving rejects to file src/bin/pg_waldump/pg_waldump.c.rej

Could you send a rebased version? In the meantime I'll switch the cf
entry to Waiting on Author.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-01-12 08:57:27 Re: DELETE CASCADE
Previous Message Pavel Borisov 2022-01-12 07:58:24 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.