| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Problem while setting the fpw with SIGHUP |
| Date: | 2018-03-20 06:30:47 |
| Message-ID: | CAFiTN-vm=SYavZUweBvR4tkjSdzG=KTuLQuyQH3MWBfa=aXY+w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 20, 2018 at 11:26 AM, Michael Paquier <michael(at)paquier(dot)xyz>
wrote:
> On Tue, Mar 20, 2018 at 10:43:55AM +0530, Dilip Kumar wrote:
> > I think like WALWriterProcess, we need to call InitXLogInsert for the
> > CheckpointerProcess as well as for the BgWriterProcess
> > because earlier they were calling InitXLogInsert while check
> > RecoveryInProgress before inserting the WAL.
>
> /* don't set signals, bgwriter has its own agenda */
> + InitXLOGAccess();
> + InitXLogInsert()
>
> This is wrong, as the checkpointer is started as well on standbys, and
> that InitXLOGAccess initializes things for WAL generation like
> ThisTimeLineID. So you should just call InitXLogInsert(), and a comment
> would be welcome for both the bgwriter and the checkpointer.
>
Yeah, you are right. Fixed.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| xlog-insert-critical-v3.patch | application/octet-stream | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2018-03-20 06:50:43 | Re: Compile error while building postgresql 10.3 |
| Previous Message | Tom Lane | 2018-03-20 06:18:54 | Re: [HACKERS] taking stdbool.h into use |