Re: error in compilation! - Mailing list pgsql-hackers

From Tom Lane
Subject Re: error in compilation!
Date
Msg-id 3878.1148757484@sss.pgh.pa.us
Whole thread Raw
In response to Re: error in compilation!  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: error in compilation!
Re: error in compilation!
Re: error in compilation!
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I am thinking it is best to always use E'' in that case.  OK?

I'm planning to revert it to the previous logic: E if there's any
backslash.  I think we have to do likewise in quote_literal() for
much the same reason: insufficient confidence that we know how
the result will be used.  (Note dblink uses quote_literal for
strings it will send to the other database.)

Currently looking through the rest of the patch.  I'm wondering
about appendStringLiteral: maybe we should kill that entirely
in favor of using PQescapeStringConn?  It's not nearly bright
enough about encoding for instance (and it *will* be used in
client-only encodings).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Fuhr
Date:
Subject: anoncvs still slow
Next
From: "Gurjeet Singh"
Date:
Subject: Re: error in compilation!