| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jürgen Strobel <juergen+postgresql(at)strobel(dot)info> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids. |
| Date: | 2015-09-15 21:32:15 |
| Message-ID: | CAB7nPqTgvZfTCACq+NZN4p7FrXeOEL3YL7zVucv2ONVZWo_Y+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | PostgreSQL : PostgreSQL 메일 링리스트 : 2015-09-15 이후 PGSQL 스포츠 토토 베트맨 21:32 |
On Tue, Sep 15, 2015 at 2:27 PM, Jürgen Strobel wrote:
> I understand this is not a bug in the sense that it displays wrong
> information, nor that I cannot get the information in a different way.
> The problem is that the proctitle functionality, which is very
> convenient and much faster than typing the SELECT above, is diminished
> by easily misleading people when it displays this id in hex encoding
> without zero padding.
Nothing prevents you to have a bash alias or a custom script doing
that. It is only a matter of minutes to have something working, and
for example psql -At will save you any parsing code you need to have
when querying ps. If you want as well to query the lag in bytes
between both nodes, simply compare the LSN position and you would get
a result in bytes.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-09-15 21:40:02 | Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids. |
| Previous Message | Jürgen Strobel | 2015-09-15 21:27:41 | Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids. |