Alexi and group,
Another good question to ask wrt alexi's question is it
good practice to everyonce in a while to reconstruct an
index from scratch. Or would a normal vacuum do the trick?
-lorenzo
---Alexei Vladishev <[EMAIL PROTECTED]> wrote:
>
> Greetings,
>
> I have an aplication which do pretty much updates/selects on table
TABLE.
> (about 3-6 updates/selects in a sec.). The TABLE has an unique
index, lets
> call it INDEX. It seems than everything works OK. But after 4-7
hours I
> get the following errors from the application - PGresult is null,
Backend
> died... After a couple of days of investigation I understood that the
> problem is in indexe, because it dies on SELECT * FROM TABLE WHERE
> zzz=33; and zzz is the unique key of the table. After dropping index
and
> recreating one problem disappers.
>
> Is there a patch to heal postgres ? Can anyone help me ?
> Thanks
>
> I am running Postgresql 6.3.2+Btree patch on Intel Linux 2.0.32
(RedHat
> 5.0).
>
> Yours sincerely,
> Alexei Vladishev
>
>
>
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
