Re: [HACKERS] Re: Bug#43221: postgresql: When disk is full, insert corrupts indices

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: Bug#43221: postgresql: When disk is full, insert corrupts indices
Date: 1999-08-23 11:12:58
Message-ID: 37C12CBA.3B7F0319@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Vadim Mikheev <vadim(at)krs(dot)ru> writes:
> > Whenever index insert fails (for _any_ reason) index may be
> ^^^^^^^^^^^^^^^^
> > corrupted. I hope to address this with WAL...
>
> One certainly hopes that's not true in the case of "cannot insert
> duplicate key into a unique index" failures !?

Oh, I meant cases when child btree page is splitted but
parent page is not updated, sorry.

BTW, duplicate check is made _before_ insertion...

Vadim
P.S. I'm on vacation till Aug 30...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zakkr 1999-08-23 11:56:31 trigger: run in transaction
Previous Message Hub.Org News Admin 1999-08-23 09:40:46