Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>
>>Here is an updated version of the COPY \x patch. It is the first patch
>>attached.
>>Also, I realized that if we support \x in COPY, we should also support
>>\x in strings to the backend. This is the second patch.
>
>
> Do we really want to do any of these things? We've been getting beaten
> up recently about the fact that we have non-SQL-spec string escapes
> (ie, all the backslash stuff) so I'm a bit dubious about adding more,
> especially when there's little if any demand for it.
>
> I don't object too much to the COPY addition, since that's outside any
> spec anyway, but I do think we ought to think twice about adding this
> to SQL literal handling.
+1 from me on this for Tom -- please don't break spec compliance!
Best Regards,
Michael Paesold