Re: COPY is not working - Mailing list pgsql-hackers

From Tom Lane
Subject Re: COPY is not working
Date
Msg-id 232.1272941475@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY is not working  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: COPY is not working
List pgsql-hackers
Jan Wieck <JanWieck@Yahoo.com> writes:
> On 4/30/2010 1:56 AM, Jaime Casanova wrote:
>> ah! this is because COPY doesn't follow inherited tables... should it?

> The TRUNCATE command's behavior was changed in that regard. What 
> TRUNCATE did in 8.3 is now TRUNCATE ONLY in 8.4. I don't see a reason 
> why COPY should not follow suit.

How about "because it's inappropriate for dump/reload, which is the main
use-case for COPY"?  In any case it'd be weird for COPY FROM and COPY TO
to behave differently on this point, but I don't really see how COPY
FROM would do anything intelligent for inheritance.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: max_standby_delay considered harmful
Next
From: Tom Lane
Date:
Subject: Re: what is good solution for support NULL inside string_to_array function?