pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Graham Wideman <gwlist@grahamwideman.com>
To: Johan_Fredrik <johanfo@ohman.no>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16182: Error in logs from "renaming temporary statistics"
Date: Thu, 13 Feb 2020 19:16:40 -0800
Message-ID: <20200214031724.85771BFEC9@mailout.easymail.ca> (raw)
In-Reply-To: <CADB9d9oODSQNAdyAhWD89A4tN7yFY9ACygQwqxdBnUKJjTCFoQ@mail.g mail.com>
References: <16182-06f613c9fd10f3bf@postgresql.org>
	<20200102140703.GA4841@paquier.xyz>
	<CADB9d9oODSQNAdyAhWD89A4tN7yFY9ACygQwqxdBnUKJjTCFoQ@mail.gmail.com>

I just wanted to add that this bug 16182 is the subject of a discussion here:

https://www.postgresql.org/message-id/flat/CAPpHfds9trA6ipezK3BsuuOSQwEmESiqj8pkOxACFJpoLpcoNw@mail....

... which started in Nov 2017, and appears to be ongoing (latest message Jan 2020). 

Alexander Korotkov 2017-11-28 reports that the problem occurs in the absence of antivirus etc.

Graham


At 1/3/2020 12:06 PM, =?UTF-8?Q?Johan_Fredrik_=C3=98hman?= wrote:
>--0000000000003cddfd059b41d8e9
>Content-Type: text/plain; charset="UTF-8"
>Content-Transfer-Encoding: quoted-printable
>
>Thanks for this informative feedback. I was thinking that antivirus was an
>explanation, but I am pretty sure the the PG data directory was on the
>antivirus exclusion list.  However, in light of this I will try to monitor
>the processes that access this file and come back to you on the findings.
>--
>JF
>
>On Thu, Jan 2, 2020 at 3:07 PM Michael Paquier <michael@paquier.xyz> wrote:
>
>> On Thu, Jan 02, 2020 at 06:55:37AM +0000, PG Bug reporting form wrote:
>> > I have checked the permissions of the folder and files, and I can not s=
>ee
>> > why this occurs.
>>
>> This error would occur on Windows when a concurrent process, external
>> to Postgres, has a file opened in non-shared mode while Postgres tries
>> to work on it.  In this case the work is done by pgrename() on
>> Postgres side which is a custom wrapper in src/port/dirmod.c to handle
>> this kind of scenarios with a retry-and-sleep logic, but it gives up
>> after 10s (100 tries of 100ms each).
>>
>> This issue could be usually caused by an antivirus or something that
>> scans the files of the disk where Postgres data is located.  In this
>> case, the best thing you could do is to prevent the concurrent
>> activity from happening by filtering out Postgres data folder.  Nobody
>> can guess why this file is held opened that long though without
>> looking at your server when the problem happens.
>> --
>> Michael
>>
>
>
>--=20
>Johan Fredrik =C3=98hman






view thread (5+ messages)  latest in thread

Message-ID: <20200214031724.85771BFEC9@mailout.easymail.ca>
Permalink:  ../20200214031724.85771BFEC9@mailout.easymail.ca/
Also on:    postgresql.org/message-id/20200214031724.85771BFEC9@mailout.easymail.ca

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: gwlist@grahamwideman.com, johanfo@ohman.no, michael@paquier.xyz
  Subject: Re: BUG #16182: Error in logs from "renaming temporary statistics"
  In-Reply-To: <20200214031724.85771BFEC9@mailout.easymail.ca>
  References: <16182-06f613c9fd10f3bf@postgresql.org> <20200102140703.GA4841@paquier.xyz> <CADB9d9oODSQNAdyAhWD89A4tN7yFY9ACygQwqxdBnUKJjTCFoQ@mail.gmail.com> <20200214031724.85771BFEC9@mailout.easymail.ca>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox