| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY is not working |
| Date: | 2010-05-04 02:51:15 |
| Message-ID: | 232.1272941475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)Yahoo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-04 02:54:36 | Re: what is good solution for support NULL inside string_to_array function? |
| Previous Message | Bruce Momjian | 2010-05-04 02:45:10 | Re: max_standby_delay considered harmful |