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

Re: [GENERAL] DELETE statement KILL backend <AGAIN>

From: Florian Wunderlich <florian(dot)wunderlich(at)tec(dot)med(dot)uni-muenchen(dot)de>
To: "David Ben-Yaacov" <David_BenYaacov(at)itd(dot)sterling(dot)com>, "Sferacarta Software" <sferac(at)bo(dot)nettuno(dot)it>, <pgsql-general(at)postgreSQL(dot)org>
Subject: Re: [GENERAL] DELETE statement KILL backend <AGAIN>
Date: 1998-08-24 17:17:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
>In my experience, the problem seems to be caused by a lot of data being put
>into the database.  We are using the database to ingest real-time data 24
>hours a day/7 days a week. The data comes in about every three minutes.
>While I was not able to identify what the exact cause has been, I have
>noticed that before the problem becomes critical (before the backend
>terminates abnormally), the (number of) indexes do not correspond to the
>actual table.  That leads me to believe that the indexes do not get created
>on all occasions.  After some time, the table's internal indexes may be come
>corrupted, and vacuuming does no good.
>When trying to fix this, I first delete the index, then recreate it., then
>vacuum.  If that doesn't work, then I drop the table, create the index,
>reload the data, and then vacuum the table.
>I would be curious to see if anyone else has had this type of problem and
>what their solutions were.

Same with us here, we use a really big database, but in my experience, it
happend only when I killed (with SIGTERM, but anyway) a single postgres
process that made an "endless" query. I think that some internal tables are
left over in the data/base directory tree, and postgres tends to get
confused about them.
Not sure about this anyway.

DROP/CREATE INDEX didn't solve this, I always did a DROP DATABASE and a
complete reload of all data, and then it worked fine again.


pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-08-24 19:18:28
Subject: Re: [HACKERS] initdb problem
Previous:From: Jouni AhtoDate: 1998-08-24 16:47:21
Subject: Re: [INTERFACES] Convert PGconn, PGresult to opaque types?

pgsql-general by date

Next:From: Shawn T. WalkerDate: 1998-08-24 17:59:29
Subject: [GENERAL] DBD::Pg
Previous:From: David Prieto CarrellanDate: 1998-08-24 16:38:29
Subject: Cursors out of a transaction

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