| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: pg_partition_tree crashes for a non-defined relation |
| Date: | 2019-03-04 18:56:00 |
| Message-ID: | 20190304185600.GA24510@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Feb-28, Alvaro Herrera wrote:
> What about legacy inheritance? I see that pg_partition_tree handles
> that case perfectly well -- it seems to return the complete hierarchy
> rooted at the given relation. However, it seems odd that it works at
> all, don't you think? Consider this:
> [...]
> I would opt for returning the empty set for legacy inheritance too.
I added tests to immortalize the current behavior for legacy inheritance
relations too. Thanks!
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-03-04 19:01:33 | Re: POC: converting Lists into arrays |
| Previous Message | Tomas Vondra | 2019-03-04 18:46:50 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |