Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows
Date
Msg-id 20191011002814.GA2373@paquier.xyz
Whole thread Raw
In response to Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On Thu, Oct 10, 2019 at 08:25:15AM -0700, Andres Freund wrote:
> I think we really ought to remove the -F from pg_regress.c, and leave
> that up to the caller. Right now it's just about impossible to
> configure without patching the source, unless I miss something.

Well, I have just posted something about that:
https://www.postgresql.org/message-id/20191009062640.GB21379@paquier.xyz

Perhaps there are better ideas for that particular problem, let's
see.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12
Next
From: PG Bug reporting form
Date:
Subject: BUG #16048: SQLSTATE 22P05 is not captured in exception clause