| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Date: | 2021-06-08 19:04:28 |
| Message-ID: | 20210608190428.GH16435@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 08, 2021 at 11:40:31AM -0700, Peter Geoghegan wrote:
> Reminds me of the other bug that you also reported about a year ago,
> Justin - which was never fixed. The one with the duplicate tids from a cic
> (see pg 14 open item).
>
> Is this essentially the same environment as the one that led to your other
> bug report?
Yes, it's on the same VM, running an internal instance of our software.
I'm not sure, but my reindex script may be more relevant than the software.
Some of the data pg_statistic data might be similar to the instances our
customers run, but much of it isn't similar.
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Christensen | 2021-06-08 19:25:49 | Re: DELETE CASCADE |
| Previous Message | Justin Pryzby | 2021-06-08 18:45:14 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |