Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: copy losing information
- 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: Thu, 27 Jul 2006 18:04:17 -0400
"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
- References:
- Re: copy losing information
- From: Silvela, Jaime \(Exchange\)
- Re: copy losing information
- Prev by Date: Re: automatic and randomally population
- Next by Date: Re: Can't start PostgreSQL
- Previous by thread: Re: copy losing information
- Next by thread: JDBC
- Indexes: