| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: recent failures on lorikeet |
| Date: | 2021-06-14 16:41:36 |
| Message-ID: | 7ae24cd8-154c-9f36-ba61-f250f2c28da6@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/14/21 12:33 PM, Andrew Dunstan wrote:
>
> The line in lmgr.c is where the process title gets changed to "waiting".
> I recently stopped setting process title on this animal on REL_13_STABLE
> and its similar errors have largely gone away. I can do the same on
> HEAD. But it does make me wonder what the heck has changed to make this
> code fragile.
Of course I meant the line (1831) in lock.c.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-06-14 16:46:34 | Re: A new function to wait for the backend exit after termination |
| Previous Message | Noah Misch | 2021-06-14 16:40:27 | Re: A new function to wait for the backend exit after termination |