Re: Incomplete pg_dump operation

Our PostgreSQL problem was too far beyond my abilities to solve it, so I solicited bids using RentACoder.com.

This problem was solved once and for all this morning by Frank Heikens at
<http://nl.linkedin.com/pub/frank-heikens/0/190/517>http://nl.linkedin.com/pub/frank-heikens/0/190/517and
<http://www.rentacoder.com/RentACoder/DotNet/SoftwareCoders/ShowBioInfo.aspx?lngAuthorId=7514248>http://www.rentacoder.com/RentACoder/DotNet/SoftwareCoders/ShowBioInfo.aspx?lngAuthorId=7514248
--and our database system's back to normal. 

Mr. Heikens isolated the one corrupted data record, created a new table, and replaced the flawed table with the new
table. I have nothing but compliments for Mr. Heikens' knowledge, professionalism, speed, accuracy, caution,
communication,and wizardry.   

-------

At 10:16 AM 2/9/2010, peter@vfemail.net wrote:

>The semicolon makes a tremendous difference.  Thank you for your patience.
>
>select * from news limit 0; displays a nice little table and 0 rows of data.
>select * from news limit 1; displays the same table and the contents of 1 data record.
>select * from news limit 5000000000; returns an "ERROR:  integer out of range" message.
>
>select * from news limit 439579; returns an "out of memory for query result" message.
>select * from news limit 439580; returns an "ERROR:  could not open relation with OID 2196359751" message.
>
>-------
>
>At 10:11 PM 2/8/2010, Tom Lane wrote:
>>peter@vfemail.net writes:
>>> None of these commands return any message of any kind:
>>
>>>      select * from news limit 1000000000
>>>      select * from news limit 1000
>>>      select * from news limit 100
>>>      select * from news limit 10
>>
>>Um .... maybe you're forgetting to terminate them with a semicolon?
>>
>>                        regards, tom lane
>
>
>
>
>--
>Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-novice