Re: Segmentation Fault in logical decoding get/peek API - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: Segmentation Fault in logical decoding get/peek API
Date
Msg-id 20190220020911.GA15532@paquier.xyz
Whole thread Raw
In response to Re: Segmentation Fault in logical decoding get/peek API  (Jeremy Finzel <finzelj@gmail.com>)
Responses Re: Segmentation Fault in logical decoding get/peek API
List pgsql-bugs
On Tue, Feb 19, 2019 at 09:32:15AM -0600, Jeremy Finzel wrote:
> I still need pg_fact_loader, but I was able to strip out any custom C code
> from the test and I am still able to produce the crash.  I dropped
> extensions pgl_ddl_deploy and pglogical_ticker.  pg_fact_loader can
> optionally use a pg background worker, but I am bypassing that and thus
> only running plpgsql functions, and still producing the crash.  This makes
> me doubt that it could have anything to do with these extensions.

The best thing which could be done is to post a set of SQL queries
on this list which allows to reproduce the problem.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15641: Autoprewarm worker fails to start on Windows withhuge pages in use Old PostgreSQL community/pgsql-bugs x