Re: BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: buschmann(at)nidsa(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows
Date: 2019-10-09 04:42:07
Message-ID: 20191009044207.GA21379@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Oct 08, 2019 at 09:09:53AM -0700, Andres Freund wrote:
> I wondered about adding something like that too. Not sure what you mean
> by directory handling problems? Couldn't that just be solved by doing an
> fstat()?

Yeah, we should just do that.

> Yuck :(. Luckily that's a pretty narrow case to hit. We really need
> windows coverage for this stuff. And also just general buildfarm
> coverage, it's not like we're immune from bugs on unixoid OSs etiher.

test_decoding hits that easily for me, and we test that on Windows for
some time now as there is a buildfarm module. That's a bit depressing.

>> Andres, others, any thoughts about this issue? Are there any
>> objections if I just fix it?
>
> Not here.

Done this one.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-10-09 09:22:05 BUG #16046: xpath returns CDATA tag along with the value in postgres 12
Previous Message Bruce Momjian 2019-10-09 01:49:55 Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented