| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <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-09 00:47:28 |
| Message-ID: | CAH2-Wz=ph4x6f3zWMaUYD=y5ujnR9ss0uzMADWYZoY2OJqC3pw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 8, 2021 at 5:18 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> I reproduced the issue on a new/fresh cluster like this:
>
> ./postgres -D data -c autovacuum_naptime=1 -c autovacuum_analyze_scale_factor=0.005 -c log_autovacuum_min_duration=-1
> psql -h /tmp postgres -c "CREATE TABLE t(i int); INSERT INTO t SELECT generate_series(1,99999); CREATE INDEX ON t(i);"
> time while psql -h /tmp postgres -qc 'REINDEX (CONCURRENTLY) INDEX t_i_idx'; do :; done&
> time while psql -h /tmp postgres -qc 'ANALYZE pg_attribute'; do :; done&
I don't have time to try this out myself today, but offhand I'm pretty
confident that this is sufficient to reproduce the underlying bug
itself. And if that's true then I guess it can't have anything to do
with the pg_upgrade/pg_resetwal issue Tom just referenced, despite the
apparent similarity.
Thanks
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-06-09 00:50:39 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Peter Geoghegan | 2021-06-09 00:44:15 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |