Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
Michael Paquier <[email protected]> Tue, 14 Jan 2020 07:33:41 +0900
| Newsgroups | gmane.comp.db.postgresql.bugs |
|---|---|
| Message-ID | <[email protected]> |
--MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Adam, On Mon, Jan 13, 2020 at 10:56:32AM -0800, Adam Scott wrote: > Thank you Michael! I know this is a late response but didn't want to > clutter the message stream until we had confirmation, but I applied this > patch to our server and could not replicate the bug. So this patch is > working for us presently. This was broken for ages, so there is a lot that has been done thanks to you because you took the time to report the bug in the first place. Tom has committed a much more paranoid (and better!) fix as of 652686a, so you will have the fix with the next minor release planned on the second week of February, 10.12 in your case. The committed patch did not include a regression test, but I am keeping track of it. -- Michael --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4c8EUACgkQnvQgOdby QH2E3A//cENag2yKUye4iliw/NZos8oklQv+T23Ipv+1Ju8dFyfOrAMYsMDl+ZPt NpGz+g5JUWQ9JIjKdbVw5sy918kCwn+suTX7zeKZsmvb5tIy/F+9iU+HOIJlGnSc FhccIJrVizyANfLUFnn2lq6r7XIQVjPt9hWjAALe4rFt2+QpvyQ2+nzYJBf9dRGf 02drUYdEcE8sB+Z0tQgGYzey6RcanjyMPzFz/NZEQGmtTfz1aMs2v2QLnG2Z+VBj EaqwbpMUk9yFzv7HObQgEXiesLGdj6fk0dqWGCBk947X2igM5ttFcIyTlSndpwxF W36U4Mv7UzngHT61/6vDQSUXmZpLH7jjvqeOFbDybrfzyC6Hi+TL4ulY2gtSpf8o LHsdKXSRCL2+Zr721OIataIHXGLDbwxsqP4uMpcuvOXJQvBaC86/9uDty1qF2Eey TtdRQ/tlzKIyzLfDioDz9DcpGbFcWEzN43iUlcf07v662cUx/FcEgeUrG7TMCi9f 2WG8l1lGSsPyrDIK8G4Ipy/RbttsLB6aS0FEstjtrl4l/dQz8dMYPVMQDb/6kDap EQaB/1l9cYcLpgyrBfpuPxQRMiZciOBt3QOcLcq8oA6AYta4kKt8kpsrnltT2kWs BFIGjHRTwkbl/sna3ksO/fqGTJDZrQwtqudu3e4zocAbjf6nUrM= =P04g -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ--