| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | alvherre(at)alvh(dot)no-ip(dot)org |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, daniele(dot)varrazzo(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
| Date: | 2022-06-21 05:59:07 |
| Message-ID: | 20220621.145907.464710049650569958.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
At Tue, 21 Jun 2022 14:56:40 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> By the way, I noticed that "libpq_pipeline uniqviol" intermittently
> fails for uncertain reasons.
>
> > result 574/575: pipeline aborted
> > ...........................................................
> > done writing
> >
> > libpq_pipeline:1531: got unexpected NULL
>
> The "...........done writing" is printed too late in the error cases.
>
> This causes the TAP test fail, but I haven't find what's happnening at
> the time.
Just to make sure, I see this with the master branch
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-06-21 06:05:02 | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
| Previous Message | Kyotaro Horiguchi | 2022-06-21 05:56:40 | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-06-21 06:05:02 | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
| Previous Message | Kyotaro Horiguchi | 2022-06-21 05:56:40 | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |