pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Willian Colognesi <willian_colognesi@trimble.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Segmentation Fault PG 14
Date: Mon, 07 Nov 2022 14:38:37 -0500
Message-ID: <3388196.1667849917@sss.pgh.pa.us> (raw)
In-Reply-To: <CADAf1kZc2ArQsTLKSaWc6eNQmFXL7LBciSEV8K23=9mZmUCemg@mail.gmail.com>
References: <CADAf1kavcN-kY=vEm3MYxhUa+rtGFs7tym5d7Ee6Ni2cwwxGqQ@mail.gmail.com>
	<3316399.1667844527@sss.pgh.pa.us>
	<CADAf1kZc2ArQsTLKSaWc6eNQmFXL7LBciSEV8K23=9mZmUCemg@mail.gmail.com>

Willian Colognesi <willian_colognesi@trimble.com> writes:
> `I take it things were okay with the version you used previously?`

> Yes, it was working pretty well in another instance with pg version
> `12.4-1.pgdg18.04+1`, and we had to make a migration of one database that
> was running in this server to another using Logical Replication.

12.4 to 14.5 is kind of a big jump :-(.

The stack trace seems to indicate that ExecProcNode transferred control
to never-never land, which says that something clobbered the function
pointer it's trying to indirect through.  I don't recall having seen
any similar reports though.

Are you using any extensions besides those that come with core Postgres?
A build incompatibility with some third-party extension might explain
this, perhaps.

One thing I'm curious about is that the stack trace seems to imply that
there was an Append plan node immediately below another Append.  That
shouldn't happen AFAIK --- the planner tries to collapse out such
cases.  Can you get us an EXPLAIN for the problem query?

			regards, tom lane





view thread (20+ messages)  latest in thread

Message-ID: <3388196.1667849917@sss.pgh.pa.us>
Permalink:  ../3388196.1667849917@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3388196.1667849917@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, willian_colognesi@trimble.com
  Subject: Re: Segmentation Fault PG 14
  In-Reply-To: <3388196.1667849917@sss.pgh.pa.us>
  References: <CADAf1kavcN-kY=vEm3MYxhUa+rtGFs7tym5d7Ee6Ni2cwwxGqQ@mail.gmail.com> <3316399.1667844527@sss.pgh.pa.us> <CADAf1kZc2ArQsTLKSaWc6eNQmFXL7LBciSEV8K23=9mZmUCemg@mail.gmail.com> <3388196.1667849917@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox