From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fixing order of resowner cleanup in 12, for Windows |
Date: | 2019-05-06 11:51:20 |
Message-ID: | CAA4eK1+O4DwdW3RL13t1S572t7tW8kRDdm7A+Gr3Whj2EHavWQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 6, 2019 at 4:41 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> On Mon, May 6, 2019 at 9:26 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> > If so, I am getting it both before and after your patch.
>
> Huh. I thought the only problem here was the phenomenon demonstrated
> by [1]. I'm a bit stumped... if we've closed all the handles in every
> backend before detaching, and then the last to detach unlinks all the
> files first and then the directory, how can we get that error?
>
Yeah, I am also not sure what caused that and I have verified it two
times to ensure that I have not made any mistake. I can try once
again tomorrow after adding some debug messages, but if someone else
can also once confirm the behavior, it would be good.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2019-05-06 12:13:22 | Re: POC: Cleaning up orphaned files using undo logs |
Previous Message | Thomas Munro | 2019-05-06 11:11:17 | Re: Fixing order of resowner cleanup in 12, for Windows |