| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [DOC] Document concurrent index builds waiting on each other |
| Date: | 2020-03-25 19:51:35 |
| Message-ID: | 20200325195135.rv7ik2ebnvt6242x@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2020-03-25 15:24:44 -0400, James Coleman wrote:
> Andres: If we got this fixed in current PG would you be opposed to
> documenting the caveat in previous versions?
Not really. I'm just not confident it's going to be useful, given the
amount of details needed to be provided to really make sense of the
issue (the earlier CIC phases don't wait for snapshots, but just
relation locks etc).
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-03-25 19:58:41 | Re: [DOC] Document concurrent index builds waiting on each other |
| Previous Message | Tom Lane | 2020-03-25 19:44:28 | Re: plan cache overhead on plpgsql expression |