From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, 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 22:27:55 |
Message-ID: | 20150303222755.GM5726@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 3, 2015 at 11:41:20AM -0600, Jim Nasby wrote:
> >>Wouldn't it need attno info too, so all 3 orderings?
> >
> >Uh, what is the third ordering? Physical, logical, and ? It already
> >gets information about dropped columns, if that is the third one.
>
> attnum; used in other catalogs to reference columns.
>
> If you're shuffling everything though pg_dump anyway then maybe it's
> not needed...
Yes, all those attno system table links are done with pg_dump SQL
commands.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-03-03 22:29:52 | Re: Proposal: knowing detail of config files via SQL |
Previous Message | Jim Nasby | 2015-03-03 22:17:40 | Re: Patch: raise default for max_wal_segments to 1GB |