James Lawrence <jljatone@gmail.com> writes:
> unfortunately pg_dump has two problems for this usecase.
> ...
> 2) column ordering within a table is inconsistent. couple of our tables
> columns get reordered (in a consistent manner) depending on which developer
> generates the schema.
> The inconsistent columns is the big problem, I suspect it is somehow
> related to the collation order of the database.
No, certainly not. Ordinarily PG will preserve column order faithfully.
The only case I know of where it will not is if you have an inheritance
relationship and the child table's columns are out of order with respect
to the parent, which generally requires having done some sort of after-
the-fact DDL on the parent. For instance
create table parent (a int, b int, c int);
create table child (d int, e int) inherits (parent);
-- at this point child has columns a, b, c, d, e
alter table parent add column f int;
-- at this point child has columns a, b, c, d, e, f
If you dump at this point, what'll be emitted is
create table parent (a int, b int, c int, f int);
create table child (d int, e int) inherits (parent);
If you restore that, the child has columns a, b, c, f, d, e, in that
order. It'd be possible for pg_dump to preserve the original ordering,
but historically it hasn't done so, and from the aesthetic standpoint
it's not clear that'd be better. After all, if you now do
create table child2 (d int, e int) inherits (parent);
then child2 is going to have a, b, c, f, d, e in either database.
I don't have enough info to say exactly how this is manifesting
as your problem, but I think you'll find it's something like that.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin