Re: BUG #8410: out of binary heap slots

From: Terje Elde <terje(at)elde(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8410: out of binary heap slots
Date: 2013-08-30 22:18:46
Message-ID: 143DCC4A-31DF-4534-8CCB-F478A0DEEFF5@elde.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Aug 30, 2013, at 11:49 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Even better explanation: The merge append is some steps below a LockRows
> node, so the number of rescans might depend on the concurrency because
> we'll do the EvalPlanQual dance on a concurrent row update.
>
> Terje, do you use read committed or repeatable read/serializable?

Using Read Committed.

Terje

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-08-30 22:22:20 Re: BUG #8410: out of binary heap slots
Previous Message Andres Freund 2013-08-30 21:49:14 Re: BUG #8410: out of binary heap slots