Re: posgres 12 bug (partitioned table) - Mailing list pgsql-bugs

From Amit Langote
Subject Re: posgres 12 bug (partitioned table)
Date
Msg-id CA+HiwqHs1DpBi5m3v1PYhw9YkaHZJaNN9Of=6Z8wAEUn9qqY3Q@mail.gmail.com
Whole thread Raw
In response to Re: posgres 12 bug (partitioned table)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Apr 23, 2021 at 3:21 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Langote <amitlangote09@gmail.com> writes:
> > On Thu, Apr 22, 2021 at 4:10 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> In the meantime, if the back branches fail with something like
> >> "virtual tuple table slot does not have system attributes" when
> >> trying to do this, that's not great but I'm not sure we should
> >> be putting effort into improving it.
>
> > Got it.  That sounds like an acceptable compromise.
>
> Hm, we're not done with this.  Whatever you think of the merits of
> throwing an implementation-level error, what's actually happening
> in v12 and v13 in the wake of a71cfc56b is that an attempt to do
> "RETURNING xmin" works in a non-cross-partition UPDATE, but in
> a cross-partition UPDATE it dumps core.

Thanks for fixing this.

-- 
Amit Langote
EDB: http://www.enterprisedb.com



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16978: Nested CTEs give ERROR in v13
Next
From: David Fetter
Date:
Subject: Re: BUG #16967: Extremely slow update statement in trigger