Re: Typo with pg_multixact/offset in multixact.c

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Typo with pg_multixact/offset in multixact.c
Date: 2018-03-22 17:36:59
Message-ID: CA+TgmoaL=LoyBATJTiN9e1eNZNMqGvOuJan+XruKN8Zm6r7K8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 5, 2018 at 2:14 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> While hacking some stuff, I bumped into the following:
> --- a/src/backend/access/transam/multixact.c
> +++ b/src/backend/access/transam/multixact.c
> @@ -1932,7 +1932,7 @@ ZeroMultiXactMemberPage(int pageno, bool writeXlog)
> * MaybeExtendOffsetSlru
> * Extend the offsets SLRU area, if necessary
> *
> - * After a binary upgrade from <= 9.2, the pg_multixact/offset SLRU area might
> + * After a binary upgrade from <= 9.2, the pg_multixact/offsets SLRU area might
> * contain files that are shorter than necessary; this would occur if the old
> * installation had used multixacts beyond the first page (files cannot be
> * copied, because the on-disk representation is different). pg_upgrade would

Committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-03-22 17:38:39 Re: Re: csv format for psql
Previous Message Robert Haas 2018-03-22 17:32:05 Re: Changing default value of wal_sync_method to open_datasync on Linux