Re: Fix of fake unlogged LSN initialization - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Fix of fake unlogged LSN initialization
Date
Msg-id CAFiTN-snKZoHXCnhW8wR+qRP-Ne+MYLTpPW9YP0=6dzCScgG6A@mail.gmail.com
Whole thread Raw
In response to RE: Fix of fake unlogged LSN initialization  ("tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>)
List pgsql-hackers
On Fri, Oct 25, 2019 at 7:42 AM tsunakawa.takay@fujitsu.com
<tsunakawa.takay@fujitsu.com> wrote:
>
> From: Dilip Kumar <dilipbalaut@gmail.com>
> > I have noticed that in StartupXlog also we reset it with 1, you might
> > want to fix that as well?
> >
> > StartupXLOG
> > {
> > ...
> > /*
> > * Initialize unlogged LSN. On a clean shutdown, it's restored from the
> > * control file. On recovery, all unlogged relations are blown away, so
> > * the unlogged LSN counter can be reset too.
> > */
> > if (ControlFile->state == DB_SHUTDOWNED)
> > XLogCtl->unloggedLSN = ControlFile->unloggedLSN;
> > else
> > XLogCtl->unloggedLSN = 1;
> >
>
> Thanks for taking a look.  I'm afraid my patch includes the fix for this part.

Oh, I missed that.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fix of fake unlogged LSN initialization
Next
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Block level parallel vacuum