From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Feature suggestions for backup and replication
Date: Tue, 8 Nov 2022 07:02:09 -0600
Message-ID: <90638847-49ea-d245-2035-dc53a2a47a61@gmail.com> (raw)
In-Reply-To: <CABigjW_PQqfMFCKBQKQoubf=jRVbbFFbRrv0xFt+GJzcmSBvkQ@mail.gmail.com>
References: <CABigjW_PQqfMFCKBQKQoubf=jRVbbFFbRrv0xFt+GJzcmSBvkQ@mail.gmail.com>
On 11/7/22 16:03, da avory wrote:
> 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
Are you using "--jobs=X --format=directory", or old school plain text dumps?
> and this would help immensely to see bottlenecks, time distribution and
> get an overall feel for which steps take how long.
While timestamps would definitely be useful, the --verbose option with
stdout *and* stderr redirected to a file plus some manual effort will answer
your questions.
>
> 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
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Feature suggestions for backup and replication
In-Reply-To: <90638847-49ea-d245-2035-dc53a2a47a61@gmail.com>
References: <CABigjW_PQqfMFCKBQKQoubf=jRVbbFFbRrv0xFt+GJzcmSBvkQ@mail.gmail.com> <90638847-49ea-d245-2035-dc53a2a47a61@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox