From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Subject: | Re: psql display of foreign keys |
Date: | 2018-12-05 01:16:33 |
Message-ID: | 20181205011633.GC2407@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-12-05 01:20:39 | Re: error message when subscription target is a partitioned table |
Previous Message | Robbie Harwood | 2018-12-04 23:46:53 | Re: [PATCH v19] GSSAPI encryption support |