Be more specific about OOM in XLogReaderAllocate
Alvaro Herrera <alvherre@alvh.no-ip.org>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/transam/xlog.c | modified | +1 −1 |
| src/backend/replication/logical/logical.c | modified | +2 −1 |
| src/backend/replication/walsender.c | modified | +2 −1 |
| src/bin/pg_rewind/parsexlog.c | modified | +3 −3 |
| src/bin/pg_waldump/pg_waldump.c | modified | +1 −1 |
Discussion
- add missing errdetail for xlogreader allocation failure error 4 messages · 2021-11-19 → 2021-11-22