Be more specific about OOM in XLogReaderAllocate
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 22 Nov 2021 16:43:43 +0000 (13:43 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 22 Nov 2021 16:43:43 +0000 (13:43 -0300)
commit2fed48f48f7f2f7a6d6f6d020f046efe3c249828
treeff31f390721e3f290f321a796b54963ec8b39e18
parent042412879e35791a65509f2786b4954a273466e5
Be more specific about OOM in XLogReaderAllocate

A couple of spots can benefit from an added errdetail(), which matches
what we were already doing in other places; and those that cannot
withstand errdetail() can get a more descriptive primary message.

Author: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: https://postgr.es/m/CALj2ACV+cX1eM03GfcA=ZMLXh5fSn1X1auJLz3yuS1duPSb9QA@mail.gmail.com
src/backend/access/transam/xlog.c
src/backend/replication/logical/logical.c
src/backend/replication/walsender.c
src/bin/pg_rewind/parsexlog.c
src/bin/pg_waldump/pg_waldump.c