| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical column ordering |
| Date: | 2015-03-03 17:24:38 |
| Message-ID: | 54F5EE56.7060903@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/3/15 11:23 AM, Bruce Momjian wrote:
> On Thu, Feb 26, 2015 at 01:55:44PM -0800, Josh Berkus wrote:
>> On 02/26/2015 01:54 PM, Alvaro Herrera wrote:
>>> This patch decouples these three things so that they
>>> can changed freely -- but provides no user interface to do so. I think
>>> that trying to only decouple the thing we currently have in two pieces,
>>> and then have a subsequent patch to decouple again, is additional
>>> conceptual complexity for no gain.
>>
>> Oh, I didn't realize there weren't commands to change the LCO. Without
>> at least SQL syntax for LCO, I don't see why we'd take it; this sounds
>> more like a WIP patch.
>
> FYI, pg_upgrade is going to need pg_dump --binary-upgrade to output the
> columns in physical order with some logical ordering information, i.e.
> pg_upgrade cannot be passed only logical ordering from pg_dump.
Wouldn't it need attno info too, so all 3 orderings?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-03-03 17:26:52 | Re: logical column ordering |
| Previous Message | Jim Nasby | 2015-03-03 17:23:31 | Re: Idea: closing the loop for "pg_ctl reload" |