Re: surppressing column names in COPY format - Mailing list pgsql-general

From Dennis Gearon
Subject Re: surppressing column names in COPY format
Date
Msg-id 3F297A21.4000501@cvc.net
Whole thread Raw
In response to Re: surppressing column names in COPY format  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I wonder if there's a way to just 'append' a temp table to another table, as long as the column's have the exact same
typeand order and don't violate constraints. It would have to be with the db shutdown probably. 

Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
>
>>the problem is that I am restoring the data to a database with different
>>column names, which errors out in 7.3 (but didn't under 7.2 since it
>>didn't produce column names in the COPY output). I checked the docs and
>>it provided no clue as to how to suppress column names for COPY only
>>dumps.
>
>
> I think you can still get it to dump as INSERTs without column names.
>
> I don't really agree that we've "lost functionality" here, though ---
> you might as well claim that it's a bug that the COPY command forces
> you to restore the data into a particular table.  If you need to do
> data transformation (which includes relabeling columns IMHO), restore
> the data into a temp table and then do INSERT ... SELECT ... to massage
> it into what you want.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>


pgsql-general by date:

Previous
From: Sergio Pili
Date:
Subject: Transactions across multiples databases
Next
From: Robert Treat
Date:
Subject: Re: surppressing column names in COPY format