| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | sk(at)zsrv(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY |
| Date: | 2022-08-15 23:56:40 |
| Message-ID: | 996031.1660607800@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> The easiest fix is likely to force all buffers to be forgotten at the end of
> index_concurrently_build() or such.
Race conditions there ...
> I don't immediately see a nicer way to fix
> this, we can't just lock the new index relation exclusively.
Why not? If the index isn't valid yet, other backends have zero
business touching it. I'd think about taking an exclusive lock
to start with, and releasing it (downgrading to a non-exclusive
lock) once the index is valid enough that other backends can
access it, which would be just before we set pg_index.indisready
to true.
Basically, this is to enforce the previously-implicit contract
that other sessions won't touch the index too soon against
careless superusers.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-08-16 00:10:27 | Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY |
| Previous Message | Andres Freund | 2022-08-15 23:39:24 | Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY |