Re: fix pg_upgrade comment

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fix pg_upgrade comment
Date: 2024-06-18 20:20:06
Message-ID: D614B25E-B549-49BD-B4D7-1DE0B87B12B7@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Jun 2024, at 21:50, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> I noticed that the "check" variable, which is used for "pg_upgrade
> --check", is commented as follows:
>
> bool check; /* true -> ask user for permission to make
> * changes */
>
> This comment was first added when pg_upgrade was introduced (commit
> c2e9b2f288), but I imagine it predates even that. I've attached a patch to
> fix this. Barring objections, I'll probably commit this soon.

Nice catch, +1 for committing.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2024-06-18 20:23:36 Re: Xact end leaves CurrentMemoryContext = TopMemoryContext
Previous Message Nathan Bossart 2024-06-18 19:50:05 fix pg_upgrade comment