Re: COPY is not working

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY is not working
Date: 2010-05-04 02:33:15
Message-ID: 4BDF876B.3000009@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/30/2010 1:56 AM, Jaime Casanova wrote:
> 2010/4/30 Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>:
>> Hi,
>>
>> COPY is not working on latest HEAD?
>> """
>> regression=# select * from a;
>> aa
>> ----
>> 32
>> 56
>> (2 rows)
>>
>> regression=# COPY a TO '/tmp/copy_test';
>> COPY 0
>> """
>>
>
> 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.

Jan

--
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-05-04 02:45:10 Re: max_standby_delay considered harmful
Previous Message Josh Berkus 2010-05-04 00:55:06 Re: what is good solution for support NULL inside string_to_array function?