Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: 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 20:18:05
Message-ID: CAB7nPqRP+BwapW4ZcfAS84-Rb3YDoCAqjss794dsOoMnv9ZM6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 15, 2015 at 3:42 AM, wrote:
> >From the last 2 lines I would guess at first glance that those processes are
> streaming segment "78" at the moment, while they really are at segment "07".
> It should be trivial to zero-pad this id.

If you can run ps as an OS user, surely you can query the master
instance for the same information, like that for example:
=# SELECT pg_current_xlog_location(),
pg_xlogfile_name(pg_current_xlog_location());
pg_current_xlog_location | pg_xlogfile_name
--------------------------+--------------------------
0/3000888 | 000000010000000000000003
(1 row)
=# SELECT write_location, pg_xlogfile_name(write_location) FROM
pg_stat_replication;
write_location | pg_xlogfile_name
----------------+--------------------------
0/3000888 | 000000010000000000000003
(1 row)
(ps displays the write location for WAL receiver processes)

Note that this is not a bug, this question is more adapted to
pgsql-general for example.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jürgen Strobel 2015-09-15 21:27:41 Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids.
Previous Message Michael Paquier 2015-09-15 18:52:24 Re: BUG #13621: Program paths are registered incorrectly.