I had this problem a few weeks ago. What I did was isolate it into an
individual row that was causing the problem, then going over the fields one by
one, till I located the free text field that was responsible. Then I repopulated it with the value in
the latest backup I could find. I wasn’t able to find any better
techniques on the web. For locating the faulty row, you might
want to write a procedural routine that will query rows sequentially. I did it in a very crude way by using
LIMIT statements till I hit the mark. As to why this happens, the suggestion I
got here was faulty hardware. Good luck From:
pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Andrzej Folek I've got a problem with conversion. |
*********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. Bear Stearns does not provide tax, legal or accounting advice. You should consult your own tax, legal and accounting advisors before engaging in any transaction. In order for Bear Stearns to comply with Internal Revenue Service Circular 230 (if applicable), you are notified that any discussion of U.S. federal tax issues contained or referred to herein is not intended or written to be used, and cannot be used, for the purpose of: (A) avoiding penalties that may be imposed under the Internal Revenue Code; nor (B) promoting, marketing or recommending to another party any transaction or matter addressed herein. ***********************************************************************