Postgres Pro
Downloads
Home   >   mailing lists

RE: [bug fix] Cascaded standby cannot start after a clean shutdown - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: [bug fix] Cascaded standby cannot start after a clean shutdown
Date
Msg-id 0A3221C70F24FB45833433255569204D1F903DF1@G01JPEXMBYT05
Whole thread Raw
In response to Re: [bug fix] Cascaded standby cannot start after a clean shutdown  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [bug fix] Cascaded standby cannot start after a clean shutdown
List pgsql-hackers
Tree view 
From: Michael Paquier [mailto:michael@paquier.xyz]
> We use palloc_extended with MCXT_ALLOC_NO_OOM in 9.5~, and malloc() further
> down, so once you remove the FATAL error caused by a record whose length
> is higher than 1GB, you discard all the hard failures, no?

Ouch, you're right.  If memory allocation fails, the startup process would emit a LOG message and continue to fetch new
WALrecords.  Then, I'm completely happy with your patch.
 

I added you as the author, and marked this as ready for committer.

Regards
Takayuki Tsunakawa

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [bug fix] Cascaded standby cannot start after a clean shutdown
Next
From: Prabhat Sahu
Date:
Subject: segmentation fault in pg head with SQL function.