From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
Date: | 2022-03-23 13:33:34 |
Message-ID: | CA+TgmoZL1jFrTm-hQ94ZTaD-+Y6P9O=Arh_KMR2WCsSJH0B3vw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 23, 2022 at 9:19 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> I think directly using smgrcreate() is a better idea instead of first
> registering and then unregistering it. I have made that change in
> the attached patch. After this change now we can merge creating the
> MAIN_FORKNUM also in the loop below where we are creating other
> fork[1] with one extra condition but I think current code is in more
> sync with the other code where we are doing the similar things so I
> have not merged it in the loop. Please let me know if you think
> otherwise.
Generally I think our practice is that we do the main fork
unconditionally (because it should always be there) and the others
only if they exist. I suggest that you make this consistent with that,
but you could do it like if (forkNum != MAIN_FORKNUM &&
!smgrexists(...)) continue if that seems nicer.
Do you think that this version handles pending syncs correctly? I
think perhaps that is overlooked.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2022-03-23 13:45:19 | Re: Add pg_freespacemap extension sql test |
Previous Message | Andrew Dunstan | 2022-03-23 13:31:04 | clean up test_rls_hooks module |