| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Arthur Silva <arthurprs(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical column ordering |
| Date: | 2015-02-27 20:09:49 |
| Message-ID: | 54F0CF0D.2070409@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tomas,
So for an API, 100% of the use cases I have for this feature would be
satisfied by:
ALTER TABLE ______ ALTER COLUMN _____ SET ORDER #
and:
ALTER TABLE _____ ADD COLUMN colname coltype ORDER #
If that's infeasible, a function would be less optimal, but would work:
SELECT pg_column_order(schemaname, tablename, colname, attnum)
If you set the order # to one where a column already exists, other
column attnums would get "bumped down", closing up any gaps in the
process. Obviously, this would require some kind of exclusive lock, but
then ALTER TABLE usually does, doesn't it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-02-27 20:14:37 | Re: logical column ordering |
| Previous Message | Pavel Stehule | 2015-02-27 20:06:44 | Re: Providing catalog view to pg_hba.conf file - Patch submission |