From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Subject: Re: psql display of foreign keys
Date: Wed, 5 Dec 2018 10:16:33 +0900
Message-ID: <20181205011633.GC2407@paquier.xyz> (raw)
In-Reply-To: <20181204184159.eue3wlchqrkh4vsc@alvherre.pgsql>
References: <23923.1543935600@sss.pgh.pa.us>
<20181204184159.eue3wlchqrkh4vsc@alvherre.pgsql>
On Tue, Dec 04, 2018 at 03:41:59PM -0300, Alvaro Herrera wrote:
> I spent a few minutes trying to think of a way of determining which
> query to use at SQL-execution time -- two CTEs, one of which would be
> short-circuited ... but I couldn't figure out how. I also tried to use
> the new pg_partition_tree() function, but it's useless for this purpose
> because it roots at its argument table, and there doesn't seem to be a
> convenient way to obtain the topmost ancestor.
This has been mentioned on the thread where pg_partition_tree has been
discussed:
https://www.postgresql.org/message-id/6baeb45a-6222-6b88-342d-37fc7d3cf89a%40lab.ntt.co.jp
It got shaved from the final patch for simplicity as we had enough
issues to deal with first. Adding a pg_partition_root or a new column
in pg_partition_tree makes sense. My guts are telling me that a
separate function is more instinctive to use.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../20181205011633.GC2407@paquier.xyz/2-signature.asc)
download
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: michael@paquier.xyz, alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org, Langote_Amit_f8@lab.ntt.co.jp
Subject: Re: psql display of foreign keys
In-Reply-To: <20181205011633.GC2407@paquier.xyz>
* 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