Typo with pg_multixact/offset in multixact.c
Started by Michael Paquierabout 8 years ago3 messageshackers
Hi all,
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
Thanks,
--
Michael
Attachments:
multixact-offset-typo.patchtext/plain; charset=us-asciiDownload+1-1
Re: Typo with pg_multixact/offset in multixact.c
On Mon, Feb 5, 2018 at 2:14 AM, Michael Paquier
<michael.paquier@gmail.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