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
