| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Jon Jensen <jon(at)endpoint(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical column position |
| Date: | 2003-11-17 18:34:36 |
| Message-ID: | 8765hioncz.fsf@mailbox.samurai.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jon Jensen <jon(at)endpoint(dot)com> writes:
> You're just saying it'd break old dumps, right? I'd assume COPY FROM
> would use attpos ordering when writing out columns, or that every
> user-visible interaction with the table pretends the columns are in
> attpos order. So dumps would break no more or less than when adding
> or dropping a column currently, right?
Right -- AFAICS, the only change in COPY compatibility would be if you
COPY TO'd a table and then changed the logical column order in some
fashion, you would no longer be able to restore the dump (unless you
specified a column list for the COPY FROM -- which, btw, pg_dump
does). I don't think it will be a problem, I just thought I'd mention
it.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ohp | 2003-11-17 19:21:11 | Connexions question |
| Previous Message | Neil Conway | 2003-11-17 18:27:32 | Re: logical column position |