Re: pl/python quoting functions - Mailing list pgsql-hackers

From Jan Urbański
Subject Re: pl/python quoting functions
Date
Msg-id 4D64E0EA.5080604@wulczer.org
Whole thread Raw
In response to Re: pl/python quoting functions  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pl/python quoting functions
List pgsql-hackers
On 22/02/11 22:48, Peter Eisentraut wrote:
> Committed this, with two changes:  Changed some things around with the
> way const char * is propagated.  Just casting it away is not nice.  Also
> dropped the error tests in the _quote.sql regression test.  This
> generates three different wordings of error messages from Python with
> 2.6, 3.1, and 3.2, which I don't care to maintain.  Maybe one day we'll
> have a better solution for this.

Thanks.

One thing: you removed the conditional pfree from PLy_quote_ident, which
makes this function leak memory if the actual quoting took place, no? Is
that leak too small to worry about?

Cheers,
Jan


pgsql-hackers by date:

Previous
From: rsmogura
Date:
Subject: Re: Binary in/out for aclitem
Next
From: Shigeru HANADA
Date:
Subject: Re: PostgreSQL FDW update