| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Fetter <david(at)fetter(dot)org>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take) |
| Date: | 2017-05-10 02:31:14 |
| Message-ID: | a0348ca6-6e03-b75f-b1b9-a667505d7232@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/05/10 6:51, Thomas Munro wrote:
> No such problem exists for partition hierarchies since the tables all
> appear as the same type to user code (though conversions may be
> happening for technical reasons).
To clarify a bit, there may exist differences in the ordering of columns,
either between the parent and its partitions or between different
partitions. For example, while parent's rowtype is (a int, b char, c
float), a partition's may be (b char, a int, c float), and yet another
partition may have (c float, a int, b char). If some user code happens to
depend on the ordering of columns, selecting from the parent and selecting
from a partition directly may return the same result but in different formats.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2017-05-10 02:43:26 | Re: idea: custom log_line_prefix components besides application_name |
| Previous Message | xu jian | 2017-05-10 02:10:28 | how to shrink pg_attribute table? |