Postgres Pro
Downloads
Home   >   mailing lists

Thread: Data now showing up

Data now showing up

From
Ken Kinder
Date:
After a few months of running, I have a database that consistantly stops
taking inserts. It isn't a high-use database, doesn't give an error, and
is really very odd. The table has one column (text) and never more than
a dozen rows.

After a while, it just stops inserting. You type an insert in psql, it
acts like it did it, you select from the data, and it's simply not there.
If I dump and rebuild the database, the problem is solved.

Any suggestions?

psql (PostgreSQL) 7.0.0

--
Ken Kinder
www.kenkinder.com

Re: Data now showing up

From
Tom Lane
Date:
Ken Kinder <ken@kenkinder.com> writes:
> After a few months of running, I have a database that consistantly stops
> taking inserts. It isn't a high-use database, doesn't give an error, and
> is really very odd. The table has one column (text) and never more than
> a dozen rows.

> After a while, it just stops inserting. You type an insert in psql, it
> acts like it did it, you select from the data, and it's simply not there.
> If I dump and rebuild the database, the problem is solved.

More details please?  We would certainly have heard of this before if
it were a generic problem.

            regards, tom lane

Re: Data now showing up

From
Ken Kinder
Date:
Someone suggested upgrading to 0.0.3, although I didn't see anything about
this problem in the history... I did.

What kind of details do we need here? It's a one-column, one-table database.
About as simple as it gets. This is on Debian/GNU Linux although it's not
the packaged Postgres, I installed it myself.

On Sun, Jan 28, 2001 at 08:14:12PM -0500, Tom Lane wrote:
> Ken Kinder <ken@kenkinder.com> writes:
> > After a few months of running, I have a database that consistantly stops
> > taking inserts. It isn't a high-use database, doesn't give an error, and
> > is really very odd. The table has one column (text) and never more than
> > a dozen rows.
>
> > After a while, it just stops inserting. You type an insert in psql, it
> > acts like it did it, you select from the data, and it's simply not there.
> > If I dump and rebuild the database, the problem is solved.
>
> More details please?  We would certainly have heard of this before if
> it were a generic problem.
>
>             regards, tom lane

--
Ken Kinder
www.kenkinder.com

Re: Data now showing up

From
Tom Lane
Date:
Ken Kinder <ken@kenkinder.com> writes:
> What kind of details do we need here? It's a one-column, one-table database.
> About as simple as it gets. This is on Debian/GNU Linux although it's not
> the packaged Postgres, I installed it myself.

Nonetheless, since you're the only one reporting anything even remotely
like this, there's got to be *something* fairly unusual about your
situation.

Have you tried pushing harder to characterize the failure?  For example,
does it matter what data you're trying to insert?  Does quitting psql
and restarting make a difference?  How about stopping and restarting the
postmaster?  How about vacuuming the table, and/or dropping/rebuilding
any indexes that may exist on it?  Does anything show up in the
postmaster log when the failure happens?  Exactly what are you doing to
conclude that the data is not there --- a plain "select * from table",
or something else?

            regards, tom lane