| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: logical column ordering |
| Date: | 2015-02-27 18:33:00 |
| Message-ID: | 54F0B85C.50708@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27.2.2015 19:23, Alvaro Herrera wrote:
> Tomas Vondra wrote:
>
>> Physical ordering is still determined by the CREATE TABLE command,
>
> In theory, you should be able to UPDATE attphysnum in pg_attribute
> too when the table is empty, and new tuples inserted would follow
> the specified ordering.
Good idea - that'd give you descriptors with
(attnum != attphysnum)
which might trigger some bugs.
--
Tomas Vondra http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-02-27 18:35:18 | Re: Providing catalog view to pg_hba.conf file - Patch submission |
| Previous Message | Stephen Frost | 2015-02-27 18:32:36 | Re: Providing catalog view to pg_hba.conf file - Patch submission |