Re: Postgresql13_beta1 (could not rename temporary statistics file)Windows 64bits - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Postgresql13_beta1 (could not rename temporary statistics file)Windows 64bits
Date
Msg-id CAEudQAonpV5xWbjvWR3cFrkrapWa1dXAhE_kU892vL-SXCm9SA@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql13_beta1 (could not rename temporary statistics file)Windows 64bits  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Postgresql13_beta1 (could not rename temporary statistics file)Windows 64bits
List pgsql-hackers

Em dom., 14 de jun. de 2020 às 23:08, Michael Paquier <michael@paquier.xyz> escreveu:
On Fri, Jun 12, 2020 at 03:15:52PM -0300, Ranier Vilela wrote:
> Posgres13_beta1, is consistently writing to the logs, "could not rename
> temporary statistics file".
> When analyzing the source that writes the log, I simplified the part that
> writes the logs a little.

FWIW, I have been running a server on Windows for some time with
pgbench running in the background, combined with some starts and stops
but I cannot see that.  This log entry uses LOG, which is the level we
use for the TAP tests and please note that there are four buildfarm
animals for Windows able to run the TAP tests and they don't seem to
show that problem either: drongo, fairywen, jacana and bowerbird.  I
may be missing something of course
Hi Michael, thsnks for answer.
Yeah, something is wrong with Postgres and Windows 10 (not server) with msvc 2019 (64 bits)
II already reported on another thread, that vcregress is failing with (float8 and partitionprune) and now these messages are showing up.
None buildfarm animal, have that combination, but as Postgres officially supports it ..

regards,
Ranier Vilela

Livre de vírus. www.avast.com.

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: 回复:how to create indexconcurrently on partitioned table
Next
From: Amit Kapila
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions