Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile
От | Michael Paquier |
---|---|
Тема | Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile |
Дата | |
Msg-id | CAB7nPqQ6r6Ye88BVN+eXWa3qJnng801m4VE151oKtnbGDF2Rtw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile
|
Список | pgsql-bugs |
On Sat, Dec 31, 2016 at 9:27 PM, Magnus Hagander <magnus@hagander.net> wrote: > So, we're still with zero ability to reproduce this problem enough to know > if it's fixed, or if other issues are caused. > > I'm thinking maybe we should push this patch to master, to at least get a > largeish number of runs with it on a bunch of different platforms. No > backpatching until we've seen it run there for some time to feel more > confident about it. > > Thoughts? Yeah, I kind of agree with that. Not reacting with an ENOENT on win32's stat() if ERROR_DELETE_PENDING is found is definitely wrong, as is not doing the mapping in win32error.c. -- Michael -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: