Re: Adjust macro name in pg_backup_stop()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Adjust macro name in pg_backup_stop()
Date: 2022-09-13 01:58:50
Message-ID: Yx/j2ok41x7U9FTO@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 12, 2022 at 05:06:16PM +0530, Bharath Rupireddy wrote:
> Hi, it looks like the commit [1] renamed pg_stop_backup() to
> pg_backup_stop() but forgot to rename the associated
> PG_STOP_BACKUP_V2_COLS macro. While this is harmless, here's a patch
> to rename the macro to be in sync with the function name.

This is the last reference to pg_start/stop_backup() in the code, so
done.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-09-13 02:13:11 Re: Background writer and checkpointer in crash recovery
Previous Message Michael Paquier 2022-09-13 01:48:49 Re: pg15b4: FailedAssertion("TransactionIdIsValid(xmax)