Tom Lane wrote:
> Joe Conway <mail@joeconway.com> writes:
>> If the return value is NULL, use errmsg if you'd like. I'd guess in most
>> instances you don't even need to bother freeing errmsg as it is in a
>> limited life memory context.
>
> Uh, you're confusing the backend environment with libpq's much more
> spartan lifestyle. errmsg will be malloc'd and it will *not* go away
> unless the caller free()s it.
Yup, just figured that out. Otherwise OK with it?
Joe