Re: Column reordering in pg_dump

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Decibel! <decibel(at)decibel(dot)org>, hernan gonzalez <hgonzalez(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Column reordering in pg_dump
Date: 2008-11-26 02:18:41
Message-ID: 20081126021841.GU4875@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas escribió:

> After some thought, it seems pretty clear, at least to me, that the
> third (hypothetical) command should not change the result of "SELECT *
> FROM tricky" (the contrary conclusion gives rise to a lot of problems,
> especially if there are other views depending on it). But what will
> "pg_dump -t tricky" output at this point? I suspect it will be
> necessary to introduce some new syntax here.

Everything that's user-visible needs to use logical positioning. That
includes pg_dump.

Changing physical positioning is purely an internal matter. A first-cut
implementation should probably just make it identical to logical
positioning, until the latter is changed by the user (after which,
physical positioning continues to reflect the original ordering). Only
after this work has been done and gotten battle-tested, we can get into
niceties like having the server automatically rearrange physical
positioning to improve performance.

Column identity is, of course, set in stone as soon as decided for the
first time.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dann Corbit 2008-11-26 02:59:25 Re: Simple postgresql.conf wizard -- Statistics idea...
Previous Message Robert Haas 2008-11-26 02:03:25 Re: Column reordering in pg_dump