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-11 00:28:14
Message-ID: 20191011002814.GA2373@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-10-11 14:03:35 BUG #16048: SQLSTATE 22P05 is not captured in exception clause
Previous Message Tomas Vondra 2019-10-10 20:40:22 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12