From: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
---|---|
To: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add backup_type to pg_stat_progress_basebackup |
Date: | 2025-07-22 09:06:52 |
Message-ID: | 20250722180652.7693a9d9720bac334c17e99c@sraoss.co.jp |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 22 Jul 2025 17:48:35 +0900
Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> wrote:
> Hi hackers,
>
> Starting with PostgreSQL 17, pg_basebackup supports incremental
> backups. However, the pg_stat_progress_basebackup view doesn't
> currently show the backup type (i.e., whether it's a full or
> incremental backup).
>
> Therefore, I propose adding a backup_type column to this view. While
> this information is available in pg_stat_activity, the backup type is
> important for monitoring the progress of pg_basebackup, and including
> it directly in the progress view would be very useful.
>
> Thoughts?
That seems reasonable to me.
Just one minor comment on the patch:
+
+ <row>
+ <entry role="catalog_table_entry"><para role="column_definition">
+ <structfield>backup_type</structfield> <type>bigint</type>
+ </para>
+ <para>
+ Backup type. Either <literal>full</literal> or
+ <literal>incremental</literal>.
+ </para></entry>
+ </row>
The type should be text rather than bigint.
Regards,
Yugo Nagata
--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2025-07-22 09:08:37 | Re: track needed attributes in plan nodes for executor use |
Previous Message | shveta malik | 2025-07-22 08:59:45 | Re: Skipping schema changes in publication |