| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
| Date: | 2016-10-06 06:31:30 |
| Message-ID: | CAB7nPqRJV6trFta-Qzgi6j2feuYR2ZC+KHvWdHnbpDG2scTrxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Oct 6, 2016 at 2:20 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> I have been digging around that, but could not find out any options
> that would delay the file deletion after it has been requested. As
> pg_basebackup grabs automatically all the files in PGDATA, I have as
> well tried to use thousands of dummy files up to 1MB, as well as huge
> files ("fsutil file createnew" is your friend), deleting them manually
> to force the stat() calls to be unhappy be still I could not reproduce
> it... If somebody has better ideas I am open.
Extra idea: patch win32_safestat() so as it continues to call stat()
in an infinite loop for a specific file that I manually created in
base/$DBOID until it fails with res < 0. Even that did not bump into
ERROR_DELETE_PENDING :)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouber Saparev | 2016-10-06 07:29:23 | Re: BUG #14354: Wrong interpretation of JSON 'null' |
| Previous Message | Michael Paquier | 2016-10-06 05:20:38 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |