| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Make pg_regress print a connstring with sockdir |
| Date: | 2017-08-29 21:44:55 |
| Message-ID: | CA+TgmobJWaLad_TvyZQpJt3GGr4eMFg-_4yPAEMLPXv-WEHicw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 28, 2017 at 7:57 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> I'm frequently debugging postmasters that are around long enough. Deadlocks,
> etc.
>
> It's also way easier to debug shmem related issues with a live postmaster vs
> a core.
Yeah. I don't *frequently* debug postmasters that hang during the
regression tests, but I definitely have done it, and I think something
like this would make it easier. Right now if something wedges and you
need to connect to the postmaster to see what's going on, you have to
grep for the pid, then lsof to get the socket directory. This would
simplify things.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-29 22:06:52 | Improve history file reasons when doing promotion |
| Previous Message | Tom Lane | 2017-08-29 21:14:31 | Re: postgres_fdw bug in 9.6 |