| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Segmentation Fault in logical decoding get/peek API |
| Date: | 2019-02-20 02:09:11 |
| Message-ID: | 20190220020911.GA15532@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2019-02-20 02:21:05 | Re: BUG #15641: Autoprewarm worker fails to start on Windows with huge pages in use Old PostgreSQL community/pgsql-bugs x |
| Previous Message | Tom Lane | 2019-02-19 21:51:46 | Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby |