Re: ANALYZE: ERROR: tuple already updated by self
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Andres Freund <andres@anarazel.de>
Cc: Justin Pryzby <pryzby@telsasoft.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-06-19T00:20:21Z
Lists: pgsql-hackers
On Tue, Jun 18, 2019 at 5:09 PM Andres Freund <andres@anarazel.de> wrote: > > It might be interesting to set a breakpoint within heap_update(), > > which is called by simple_heap_update() --technically, this is where > > the reported failure occurs. From there, you could send an image of > > the page to the list by following the procedure described here: > Hm, what are you hoping to glean by doing so? Nothing in particular. I see no reason to assume that we know what that looks like, though. It's easy to check. -- Peter Geoghegan
Commits
-
Don't build extended statistics on inheritance trees
- 859b3003de87 10.10 landed
- 4dbf70b2ff1e 11.5 landed
- e1947f6c3ed8 12.0 landed
- 14ef15a22246 13.0 landed