> Date: Thu, 26 Jun 2008 14:29:04 -0400
> From: Andrew Sullivan <ajs at crankycanuck.ca>
> Subject: Re: [Slony1-general] Logshipping dump import failure
> To: slony1-general at lists.slony.info
> Message-ID: <20080626182904.GF28168 at crankycanuck.ca>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Jun 26, 2008 at 01:13:43PM -0500, Troy Wolf wrote:
>> I have not had a response to the error I received when trying to
>> subscribe a third node to my set. So in the meantime, I'm
>
> I didn't reply because I'm mystified.  It looked right to me.
>
>> The import is failing, and it appears it is choking on an array
>> column. That is, I have a table with a column that has a data type of
>> text[] -- which is an array. In the dump, this is represented as
>> {a,b,c}. If I take the line that the import is choking on and remove
>> that column, it works.
>>
>> Thoughts?
>
> If you dump the table itself, what does that line say?  This also looks
> right to me.

First, the failure was not truly because of the array as it turns out.
When doing psql import, you have to look at the FIRST error...not the
last error that is visible. Only the first error tells you why the
import actually failed. My problem was simply constraint issues
requiring me to import the tables in a specific order.

I'm not sure why my command-line copy test "proved" that the array
column fails. I must not know how to do that correctly? Argh. Sorry to
waste some of your time.