From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | olly(at)lfix(dot)co(dot)uk, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problem with COPY in 8.0.3 |
Date: | 2005-10-13 00:56:51 |
Message-ID: | 20051013005651.GA71419@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Oct 12, 2005 at 07:28:37PM -0400, Tom Lane wrote:
> Oliver Elphick <olly(at)lfix(dot)co(dot)uk> writes:
> > On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote:
> >> Hm. Could we see the actual pg_attribute data for both this table and
> >> its parent?
>
> > Here you are:
>
> Thanks. Nothing particularly strange-looking there though. Do you want
> to try tracing through COPY with a debugger to see where it's getting
> the bogus column order from?
Do you get the same bogosity with the attached test case? It's
based on the same table definition and data from your first message;
about the only differences from what you're doing are that the table
isn't inherited and it uses "COPY foo FROM stdin" instead of reading
the data from an external file. If this test works correctly, what
happens if you use "COPY FROM stdin" on the real table?
--
Michael Fuhr
Attachment | Content-Type | Size |
---|---|---|
test.sql | text/plain | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-10-13 02:24:53 | Re: BUG #1953: trigger action on delete |
Previous Message | Menno Smits | 2005-10-13 00:19:58 | BUG #1958: Postmaster doesn't close open file handles on startup |