| From: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16161: pg_ctl stop fails sometimes (on Windows) |
| Date: | 2019-12-19 20:49:54 |
| Message-ID: | CAC+AXB2zUJjW5cPbC+Oa9t0EOJ=+NpZsKFUDQsvAUxc40UNsYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Dec 19, 2019 at 9:09 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > It seems that the check for ERROR_DELETE_PENDING was added to
> > pgwin32_safestat() blindly, the issue wasn't reproduced at that time:
> >
> https://www.postgresql.org/message-id/CAB7nPqRJV6trFta-Qzgi6j2feuYR2ZC%2BKHvWdHnbpDG2scTrxw%40mail.gmail.com
>
> Hmm, makes one wonder whether that's actually live code.
>
>
Part of what the patch "Windows could not stat file - over 4GB" [1] does is
proposing an alternative using native functions.
[1] https://commitfest.postgresql.org/26/2189/
Regards,
Juan José Santamaría Flecha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | TAKATSUKA Haruka | 2019-12-20 01:19:52 | Re: BUG #16172: failure of vacuum file truncation can cause permanent data corruption |
| Previous Message | Tom Lane | 2019-12-19 20:09:45 | Re: BUG #16161: pg_ctl stop fails sometimes (on Windows) |