From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
Date: Sun, 10 Feb 2019 17:54:49 -0300
Message-ID: <20190210205449.GA10870@alvherre.pgsql> (raw)
In-Reply-To: <CAH2-Wz=vi2Oq=d+j6Ya6yj_ud9ekCwOQDkEqTG9XLxhZPGN0ng@mail.gmail.com>
On 2019-Feb-10, Peter Geoghegan wrote:
> On Sun, Feb 10, 2019 at 8:13 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Just to be be clear, my inclination is to do nothing about this in v11.
> > It's not apparent to me that any fix is possible given the v11 dependency
> > data, at least not without downsides that'd likely outweigh the upsides.
> > We've not seen field complaints about these problems.
>
> I thought that you might have had a trick up your sleeve for v11,
> although I had no idea how that would be possible without making sure
> that partition dependencies came in pairs to begin with. :-)
If we disregard the scenario were people downgrade across minor
versions, it's likely possible to produce SQL queries to transform from
the old arrangement to the new one, and include those in release notes
or a wiki page; not for this week's minors (ENOTIME) but maybe for the
next one.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, pg@bowt.ie, tgl@sss.pgh.pa.us
Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
In-Reply-To: <20190210205449.GA10870@alvherre.pgsql>
* 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