From: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Orphaned relation files after crash recovery |
Date: | 2020-02-17 11:23:15 |
Message-ID: | CA+fd4k5Cao1ociMaSM8A776-wF4uYv54H+jDZ0+Lvn=Cjn7Cdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 17 Feb 2020 at 20:05, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> On Mon, Feb 17, 2020 at 11:20 PM Masahiko Sawada
> <masahiko(dot)sawada(at)2ndquadrant(dot)com> wrote:
> > Is this a bug? Has this ever been discussed?
>
> Hi Sawada-san,
>
> There was this thread:
>
> https://www.postgresql.org/message-id/flat/CAEepm%3D0ULqYgM2aFeOnrx6YrtBg3xUdxALoyCG%2BXpssKqmezug%40mail.gmail.com
>
> We chose that as a sort of simple test case to demonstrate the
> machinery for performing any kind of clean-up work when when a
> transaction aborts, even if there is a crash restart in between. It's
> going to take a little while to come back to that due to some on-going
> redesign work on the undo proposal.
Thank you! That's a good use case of undo logging. I'm looking forward
to the new patch.
Regards,
--
Masahiko Sawada http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-02-17 11:55:12 | Re: tiny documentation fix |
Previous Message | Amit Kapila | 2020-02-17 11:19:22 | Re: Parallel copy |