Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids.
От | Michael Paquier |
---|---|
Тема | Re: BUG #13620: Streaming replication process titles should use zero padding for TX ids. |
Дата | |
Msg-id | CAB7nPqRP+BwapW4ZcfAS84-Rb3YDoCAqjss794dsOoMnv9ZM6g@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #13620: Streaming replication process titles should use zero padding for TX ids. (juergen+postgresql@strobel.info) |
Ответы |
Re: BUG #13620: Streaming replication process titles should
use zero padding for TX ids.
|
Список | 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
В списке pgsql-bugs по дате отправления: