| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Silvela, Jaime \(Exchange\)" <JSilvela(at)bear(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Reece Hart" <reece(at)harts(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: copy losing information |
| Date: | 2006-07-27 22:04:17 |
| Message-ID: | 12925.1154037857@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Silvela, Jaime \(Exchange\)" <JSilvela(at)bear(dot)com> writes:
> Tom, how and why would INSERTs be dropped on the client side?
[ shrug... ] I don't know your code; I was thinking about garden variety
bugs in your ruby script. However, if you can make it happen just
through psql \copy then that theory seems to lose its luster :-(
Something else that might be worth looking at: have you got any
user-written BEFORE INSERT triggers on that table? A trigger that
sometimes returned NULL would explain the symptoms.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Johnson | 2006-07-27 22:26:42 | Re: Can't start PostgreSQL |
| Previous Message | Shoaib Mir | 2006-07-27 21:56:38 | Re: automatic and randomally population |