public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Zhihong Yu <[email protected]>
Cc: 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: Mon, 17 Jan 2022 13:29:20 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALNJ-vQgAroyjsKi4=2UFQiU+NGMNo7GQ1-VO5v_LGNke3GmWg@mail.gmail.com>

On 2022-Jan-17, Zhihong Yu wrote:

> On Mon, Jan 17, 2022 at 6:26 AM Alvaro Herrera <[email protected]>
> wrote:

> > On 2022-Jan-17, Amit Langote wrote:

> > The other is suggested by you:
> >
> > > Another thing to consider is that we haven't seen many reports of the
> > > problem (UPDATEs of partitioned PK tables causing DELETEs in
> > > referencing tables), even though it can be possibly very surprising to
> > > those who do run into it.
> >
> > Do nothing in the old branches.

> I think option 2, not backpatching, is more desirable at this stage.

Preliminarly, I tend to agree.

-- 
Álvaro Herrera              Valdivia, Chile  —  https://www.EnterpriseDB.com/

view thread (3+ 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], [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