Re: Comfortably check BackendPID with psql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Naoya Anzai <nao-anzai(at)xc(dot)jp(dot)nec(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com>
Subject: Re: Comfortably check BackendPID with psql
Date: 2015-07-07 14:17:39
Message-ID: 24608.1436278659@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Pushed the patch. I only made a minor belt-and-suspenders type of
> change, namely to check whether PQbackendPID() returns 0 and not print
> that and replaced PID by pid in the docs and comments.

I would s/pid/process ID/ in the docs. "PID" is not a particularly
user-friendly term, and it's even less so if you fail to upper-case it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sawada Masahiko 2015-07-07 14:18:05 Re: Freeze avoidance of very large table.
Previous Message Fujii Masao 2015-07-07 14:08:43 Re: [PATCH] Add missing \ddp psql command