Andrew Dunstan <and...@dunslane.net> writes: > Tom said: >> 2. A slightly cleaner fix for this should be to duplicate the SV and >> then release the copy around the SvPVutf8 call, only if it's readonly. >> "Fixing" it in do_util_elog is entirely the wrong thing.
> How do we tell if it's readonly?
SvREADONLY(sv) macro.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
