Re: Changing column order through dump and restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alex Stanier <Alex(dot)stanier(at)proactis(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Changing column order through dump and restore
Date: 2016-06-27 20:56:17
Message-ID: 6441.1467060977@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Alex Stanier <Alex(dot)stanier(at)proactis(dot)com> writes:
> # Dump the database (schema only)
> pg_dump -s my_database > my_database_schema.dmp
> # Dump the database (data only) as insert statements and with commands to disable triggers
> pg_dump -a --disable-triggers --column-inserts my_database > my_database_data.dmp

> I understand the data restore will be slow (due to the inefficiency of
> the INSERT statements), but is this a valid way to go about column
> re-ordering?

FWIW, you shouldn't need to use --column-inserts mode, because even in
default COPY output, pg_dump emits column name lists in the COPY commands.
So the right things should happen when reloading into a database with
modified column order.

Haven't thought about it in great detail, but your plan sounds generally
sane otherwise.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alex Stanier 2016-06-28 08:10:21 Re: Changing column order through dump and restore
Previous Message Alex Malek 2016-06-27 18:27:32 Re: problems using pg_start_backup/pg_stop_backup and pg_basebackup at same time