Re: pg_basebackup fails on databases with high OIDs
Michael Paquier <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jan 06, 2020 at 09:07:26AM +0100, Peter Eisentraut wrote: > This is a new bug in PG12. When you have a database with an OID above > INT32_MAX (signed), then pg_basebackup fails thus: Yep. Introduced by 6b9e875. > pg_basebackup: error: could not get write-ahead log end position from > server: ERROR: value "3000000000" is out of range for type integer > > The cause appears to be commit 6b9e875f7286d8535bff7955e5aa3602e188e436. > > A possible fix is attached. An alternative to using OidInputFunctionCall() > would be exporting something like oidin_subr(). I think that you would save yourself from a lot of trouble if you do the latter with a subroutine. Not quite like that based on the process context where the call is done, but remember 21f428eb.. -- Michael
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4S7eUACgkQnvQgOdby QH2/jQ//bfgpFh/Urv/LXZcarWkYQCOs8h0ziPcmqvdaOHz5ui5GJmbAvyl+C81f Agd4lfn3T6HvEw6oEoQM/wuFFDKn5KZhVTIGLKw8whdHDrG4Tr06k54CrEgjebMQ pTEOkyTT0CMpQU9yK/ij73tjNUxjXlzKRW2XkIKA/DK6tVx8XXEPrB1aGFmSee1u HEy/sKLvzjqzmNhjpQH2PD79wxw2WNNXzjx0kg/3PNgxpnIak4HsAsApgkxeyaLj U+oidgVNoL3DUVEj0LuRQFW8ex5mFe6z6hwlu/0+VYfBKr8+AhlDFOpkNCwliXK8 KU9UhooyPl8uMEP6oPdcF5Jbn4CheXYsWSRBlyDR/L0zomYKbax3+wvDFlEQtHNr IjAtez4htWhIWOCvtXNQAld3EzH6xGRtJT0KNwqgr/fY1QmFH+HtRKSQs+bX5BYm 7LiCKx1lTFZ9z58b6R6BmT0vzKsB2XIZho6cbdzTE0Met2fVWmfVaY6t81xepNg/ FOPUBCmnWtaBYXF9RlNcDtTrFYMOVCEfvf0IsgsR0wQ/CnYh4r9zRk8qCs1MsvCH ZiixqBfOdQsg7zNQaGTpTXtyvo8oxX1Nlzw0HYBqQxLSzSKDa/KNYsfJbdD9BOIV 8GJUlzvfZq4QxIX9kgikZ2Kc2uiW74RjmsT/HeHV4Piy7+MRPIQ= =WaU7 -----END PGP SIGNATURE-----