Feature suggestions for backup and replication

From: da avory <dean(dot)avory(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Feature suggestions for backup and replication
Date: 2022-11-07 22:03:51
Message-ID: CABigjW_PQqfMFCKBQKQoubf=jRVbbFFbRrv0xFt+GJzcmSBvkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

not sure whether this is the right list to ask. I do have two (small!?)
feature suggestions, both regarding backup and replication, which might
appeal to a wider audience.

1) it would be very great to have the option to add a timestamp to all
lines of output of pg_dump and pg_restore. We regularly do dump/restores
that take multiple days and this would help immensely to see bottlenecks,
time distribution and get an overall feel for which steps take how long.

2) It would be equally great to be able to retrieve the actual value of
recovery_min_apply_delay config parameter that is configured on a streaming
client as a value on the primary (as a field in pg_stat_replication).
Ideally in a consistent form, i.e. converted to seconds or interval. We
currently have our ops team monitoring our streaming clients in various
monitoring views and while we can of course see pending transfer and replay
volume there is no way to see the intended apply_delay without storing it
somewhere on the primary (where it will get inevitably out of sync with the
used value).

Many thanks

Dean

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pilar de Teodoro 2022-11-07 22:11:22 Re: postgres replication without pg_basebackup? postgres 13.3
Previous Message Rob Sargent 2022-11-07 21:42:20 Re: Setting up replication on Windows, v9.4