| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Naoya Anzai <nao-anzai(at)xc(dot)jp(dot)nec(dot)com> |
| Cc: | "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-06-11 21:05:13 |
| Message-ID: | 5579F809.4000103@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/11/15 4:55 AM, Andres Freund wrote:
> Hi,
>
> On 2015-06-11 09:41:17 +0000, Naoya Anzai wrote:
>> This is a so tiny patch but I think it is very useful for hackers and DBAs.
>> When we debug with psql, we frequently use "SELECT pg_backend_pid();".
>> This can change the input of the 24 characters to the only 4 characters!
>
> Not a big fan of that abbreviation itself. What I'd wondered about
> instead - and actually had patched into my psql at some point - is
> adding an appropriate escape to psql's PROMPT. I think that'd serve your
> purpose as well?
+3.14159; that would be hugely helpful when using gdb.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-06-11 21:17:54 | Re: 9.5 release notes |
| Previous Message | Robert Haas | 2015-06-11 21:04:53 | Re: The purpose of the core team |