Skip site navigation (1) Skip section navigation (2)

Table Corruption

From: "mike focosi" <mike(at)goldendome(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Table Corruption
Date: 2000-11-09 16:38:39
Message-ID: 00ce01c04a6b$880503c0$2a252fd0@goldendome.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
I have several php scripts that allow my clients to add stories to a
database. I've noticed that once in a while, when they attempt to
insert/update more than 8k into a table, the table is becoming corrupted.
When a select is done on the table, the database hangs. When this happens to
one table in one database, it brings down the whole postgreSQL server
backend. Not good.

I've created a database with the same scheme/data and have only been able to
recreate the problem once. Can't seem to do it everytime. PostgreSQL usually
gives the "PQsendQuery() -- query is too long..." error and just doesn't
follow thru with the query which is fine. I can deal with limiting my
clients to less than 8k stories. But sometimes the  table gets corrupted by
a query that shouldn't be executed (ie: stopped at the too long warning).
Has anybody ever had any problems like the one I described. I've yet to
upgrade our database servers to 7+ (running 6.4) so I'm hoping maybe that
would solve the problem. But I'd like to know what the exact problem is.

thanks
-mike

mike focosi
senior applications developer
golden dome media
http://www.goldendomemedia.com
http://www.surfmichiana.com
http://www.wndu.com


Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2000-11-09 17:19:47
Subject: Re: Table Corruption
Previous:From: Peter EisentrautDate: 2000-11-09 15:53:47
Subject: Re: [SQL] alter pg_shadow

pgsql-general by date

Next:From: Josh BerkusDate: 2000-11-09 16:40:41
Subject: Requests for Development
Previous:From: Peter EisentrautDate: 2000-11-09 16:33:53
Subject: Re: need an information on PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group