| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Fwd: Re: dblink patches for comment] |
| Date: | 2009-06-06 17:42:24 |
| Message-ID: | 4A2AAA80.9060905@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> The quoting logic is still completely the wrong thing :-(. For one
> thing, quote_literal will try to generate E'' syntax in some cases.
> But more to the point, quote_literal's quoting rules don't match
> what is needed. A look at libpq's conninfo_parse says that what it
> accepts is single-quoted strings in which backslash quotes the next
> character. It does not recognize doubled single quotes. I think
> you will need to whip up a special-purpose quoting subroutine.
OK, I see that. I assume I need to care for encoding issues? If so, do I
assume server encoding or client encoding?
>> + return pstrdup(buf->data);
>
> is a waste of time. The StringInfo's buffer is already palloc'd.
Thanks -- will fix.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-06 17:51:07 | Re: [Fwd: Re: dblink patches for comment] |
| Previous Message | Tom Lane | 2009-06-06 17:22:36 | Re: PostgreSQL Developer meeting minutes up |