Re: making relfilenodes 56 bits

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: making relfilenodes 56 bits
Date: 2022-07-12 20:35:46
Message-ID: CA+TgmobAkpSJkAWbJxpe6kJC9aTNJd=KAntW6MBd3EizGYLMcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 12, 2022 at 1:09 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> What does currently happen if we exceed that?

elog

> > diff --git a/src/include/utils/wait_event.h b/src/include/utils/wait_event.h
> > index b578e2ec75..5d3775ccde 100644
> > --- a/src/include/utils/wait_event.h
> > +++ b/src/include/utils/wait_event.h
> > @@ -193,7 +193,7 @@ typedef enum
> > WAIT_EVENT_LOGICAL_REWRITE_TRUNCATE,
> > WAIT_EVENT_LOGICAL_REWRITE_WRITE,
> > WAIT_EVENT_RELATION_MAP_READ,
> > - WAIT_EVENT_RELATION_MAP_SYNC,
> > + WAIT_EVENT_RELATION_MAP_RENAME,
>
> Very minor nitpick: To me REPLACE would be a bit more accurate than RENAME,
> since it includes fsync etc?

Sure, I had it that way for a while and changed it at the last minute.
I can change it back.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-07-12 20:51:44 Re: pg15b2: large objects lost on upgrade
Previous Message Tom Lane 2022-07-12 20:31:39 Re: should check interrupts in BuildRelationExtStatistics ?