| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | os(at)ohmu(dot)fi |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8470: 9.3 locking/subtransaction performance regression |
| Date: | 2013-12-23 20:06:28 |
| Message-ID: | 20131223200628.GL22570@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera wrote:
> Please *note the behavior change* of HeapTupleSatisfiesUpdate: it will
> now return HeapTupleBeingUpdated when a tuple is locked by an Xid that's
> a subtransaction of the current top transactionn. That case previously
> returned HeapTupleBeingUpdated. If someone wants to say that we
> shouldn't change that in 9.3, please speak up. But do note that it was
> already returning that valu ewhen the lock was a multixact, so the new
> behavior can be said to be more consistent.
I hate to keep replying to myself, but above I intended to say "that
case previously returned HeapTupleMayBeUpdated".
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-23 21:40:57 | Re: BUG #8698: cast and view |
| Previous Message | Alvaro Herrera | 2013-12-23 19:53:00 | Re: BUG #8470: 9.3 locking/subtransaction performance regression |