Re: [SPAM] Re: BUG #13143: Cannot stop and restart a streaming server with a replication slot

From: Patrice Drolet <pdrolet(at)infodata(dot)ca>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [SPAM] Re: BUG #13143: Cannot stop and restart a streaming server with a replication slot
Date: 2015-04-27 16:50:32
Message-ID: D8851338-DC7E-4746-A6DF-DFDBB4E255C4@infodata.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Windows, this is really easy to have this problem : create a replication slot then try to restart the server. The server will refuse to start.

I checked the file it was not read only. There is nothing I could do to the file or the directory to succeed in restarting pg.

I put fsync=off and I could start pg. but this is not a good permanent solution!

Envoyé de mon iPad

> Le 2015-04-27 à 12:00, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> a écrit :
>
> Andres Freund wrote:
>>> On 2015-04-27 11:44:47 -0300, Alvaro Herrera wrote:
>>> I think this is failing in the fsync_fname() call in slot.c line 1045
>>> (REL9_4_STABLE).
>>
>> Patrice has since replied with log_error_verbosity=verbose logs, but
>> that reply is probably still stuck in moderation:
>
> Ah, sorry about that. Approved.
>
>> Hm. I wonder if it's maybe that the file is opened with O_RDONLY? The
>> OSs I have access to don't care - for good reason imo, fsync isn't a
>> write - but it's not inconceivable that windows might.
>
> Ah, fsync_fname() explicitely defends against this.
>
>> So that's easy enough fixed.
>
> Nice.
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2015-04-27 18:15:37 Re: pg_get_constraintdef failing with cache lookup error
Previous Message Robert Haas 2015-04-27 16:40:48 Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated)