| From: | Stefan Fercot <stefan(dot)fercot(at)dataegret(dot)com> |
|---|---|
| To: | Stepan Neretin <sndcppg(at)gmail(dot)com> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Recovery of .partial WAL segments |
| Date: | 2024-10-18 12:39:26 |
| Message-ID: | CAPzjO7VYFFeeMAFL4j2JsDTtDGG2FdnOXU5LN+JrbbkKrvr=ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Fri, Oct 18, 2024 at 11:07 AM Stepan Neretin <sndcppg(at)gmail(dot)com> wrote:
> Hi there! It looks good to me!
>
Thanks!
But I have a question. How is the partialxlogfname freed in case of an
> error?
I'm not sure I understand your question. What kind of error would you
expect exactly?
I mostly added a pfree there because we don't need it further. But why
would it be more of a problem compared to other variables/pointers?
Kind regards,
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2024-10-18 12:42:43 | Re: Amcheck verification of GiST and GIN |
| Previous Message | Shubham Khanna | 2024-10-18 12:15:22 | Re: Pgoutput not capturing the generated columns |