public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Amit Langote <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: Ibrar Ahmed <[email protected]>
Cc: Arne Roland <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: Masahiko Sawada <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: Rahila Syed <[email protected]>
Cc: Tomas Vondra <[email protected]>
Subject: Re: a misbehavior of partition row movement (?)
Date: Tue, 11 Jan 2022 08:23:41 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+HiwqF2PeNde2Qc8AH_D+KX7to_f94KERAKmZfiSejU-tprZA@mail.gmail.com>
On 2022-Jan-11, Amit Langote wrote:
> As for the fix to make cross-partition updates work correctly with
> foreign keys, I just realized it won't work for the users' existing
> foreign keys, because the parent table's triggers that are needed for
> the fix to work would not be present. Were you thinking that we'd ask
> users of v13 and v14 to drop and recreate those constraints?
Yeah, more or less. Also, any tables created from 13.6 onwards.
I was mainly thinking that we'll still have people creating new clusters
using pg13 for half a decade.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended." (Gerry Pourwelle)
view thread (5+ messages) latest in thread
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: a misbehavior of partition row movement (?)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox