| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rare link canary failure in dblink test |
| Date: | 2020-08-30 14:48:42 |
| Message-ID: | 3792338.1598798922@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> A couple of recent cases where an error "libpq is incorrectly linked
> to backend functions" broke the dblink test:
lorikeet seems just plain unstable these days :-(. Don't know why.
> ... curiously the message also appeared a
> couple of times on two Unixen. Perhaps we can write those off as lost
> in the mists of time.
No, those were expected, because they ran between ed0cdf0e0, which
intentionally introduced this error, and e3d77ea6b and 4fa3741d1
which fixed it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-08-30 15:03:15 | Re: Disk-based hash aggregate's cost model |
| Previous Message | David CARLIER | 2020-08-30 13:03:32 | [PATCH v1] explicit_bzero.c: using explicit_memset on NetBSD |