Re: BUG #15460: Error while creating index or constraint
От | Peter Geoghegan |
---|---|
Тема | Re: BUG #15460: Error while creating index or constraint |
Дата | |
Msg-id | CAH2-Wzm=jR+=3YHWoNkaSNaTT-8Mqd7e+XD0VBM2Zh1vqdfZAA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #15460: Error while creating index or constraint (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: BUG #15460: Error while creating index or constraint
Re: BUG #15460: Error while creating index or constraint |
Список | pgsql-bugs |
On Mon, Oct 29, 2018 at 2:11 PM Peter Geoghegan <pg@bowt.ie> wrote: > This first line looks like it might be interesting: > > LOG: could not rmdir directory > "base/pgsql_tmp/pgsql_tmp5088.0.sharedfileset": Directory not empty > ERROR: could not determine size of temporary file "0" (Thomas Munro is CC'd here.) > I suppose that this could actually just be a result of the ERROR; the > exact order isn't a reliable indicator of the sequence of events > across processes (A useful log_line_prefix setting might clear this up > if you collect the trace_sort output again). Hmm. So apparently Windows has a habit of setting an ENOTEMPTY errcode when rmdir'ing a directory that somebody merely has a handle to. It could just be that somebody has a Windows Explorer window open -- you still get ENOTEMPTY [1]! Not sure if this is truly relevant to the problem at hand, but it seems worth being aware of. [1] https://github.com/gruntjs/grunt-contrib-clean/issues/66 -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: