Re: VACUUM's "No one parent tuple was found", redux

From: Barry Lind <barry(at)xythos(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: VACUUM's "No one parent tuple was found", redux
Date: 2002-08-13 16:09:16
Message-ID: 3D592F2C.3050002@xythos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>
>Also, for Mario and Barry: does this test case look anything like what
>your real applications do? In particular, do you ever do a SELECT FOR
>UPDATE in a transaction that commits some changes, but does not update
>or delete the locked-for-update row? If not, it's possible there are
>yet more bugs lurking in this.
>
This certainly seems plausible for my application.

--Barry

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-13 16:09:22 Re: Temporary Views
Previous Message Teodor Sigaev 2002-08-13 16:08:52 Re: Please, apply patch for contrib/tsearch