| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE: ERROR: tuple already updated by self |
| Date: | 2019-06-19 00:20:21 |
| Message-ID: | CAH2-Wzn14zz+ZNLmfWQB_SBQNpdBkgPFtEEoV6XxPYa1PUzcKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 18, 2019 at 5:09 PM Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-06-19 00:38:34 | Re: ANALYZE: ERROR: tuple already updated by self |
| Previous Message | Tom Lane | 2019-06-19 00:16:50 | Re: ANALYZE: ERROR: tuple already updated by self |