Hi,
It seems like some of the XLogReaderAllocate failure check errors are
not having errdetail "Failed while allocating a WAL reading
processor." but just the errmsg "out of memory". The "out of memory"
message without the errdetail is too generic and let's add it for
consistency and readability o
> On 19 Nov 2021, at 04:59, Bharath Rupireddy
> wrote:
> It seems like some of the XLogReaderAllocate failure check errors are
> not having errdetail "Failed while allocating a WAL reading
> processor." but just the errmsg "out of memory". The "out of memory"
> message without the errdetail is t
Le lun. 22 nov. 2021 à 19:58, Daniel Gustafsson a écrit :
> > On 19 Nov 2021, at 04:59, Bharath Rupireddy <
> bharath.rupireddyforpostg...@gmail.com> wrote:
>
> > It seems like some of the XLogReaderAllocate failure check errors are
> > not having errdetail "Failed while allocating a WAL reading
On 2021-Nov-19, Bharath Rupireddy wrote:
> It seems like some of the XLogReaderAllocate failure check errors are
> not having errdetail "Failed while allocating a WAL reading
> processor." but just the errmsg "out of memory". The "out of memory"
> message without the errdetail is too generic and l