| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add json(b)_to_tsvector function |
| Date: | 2018-04-07 19:15:24 |
| Message-ID: | 11376.1523128524@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-04-07 21:53:01 +0300, Teodor Sigaev wrote:
>> test select_parallel ... FAILED
>>
>> I don't understand how it's connected to json_to_tsquery. Can somebody point
>> me what I'm missing?
> Given that it "only" failed during upgrade check, not the earlier
> parallel check, it is possible that it's entirely unrelated and just a
> low likelihood event?
Yes. We've seen that exact symptom before:
https://www.postgresql.org/message-id/7752.1515284083@sss.pgh.pa.us
I have a suspicion that it's related to the significantly-more-common
plan instability we've been seeing in postgres_fdw.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-04-07 20:01:21 | pgsql: Indexes with INCLUDE columns and their support in B-tree |
| Previous Message | Teodor Sigaev | 2018-04-07 19:03:24 | Re: pgsql: Add json(b)_to_tsvector function |