Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> Hang on a second. Has someone considered the encoding issues this might
> suffer from, same as PQescapeString?
That was the point I raised when I saw the commit.
My advice is we shouldn't have PQescapeIdentifier at all.
PQescapeIdentifierConn would be the thing to define,
parallel to PQescapeStringConn.
regards, tom lane