From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Jeff Davis <jdavis-pgsql(at)empires(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: escape string type for upcoming 8.1 |
Date: | 2005-08-11 04:18:54 |
Message-ID: | 18124.1123733934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> What I'm asking about is, are there going to be user applications that were
> working fine in previous versions but suddenly start breaking when this change
> is made? Does that affect your decision in whether to backport this to 8.0.x?
It's worth noting that the E'...' syntax does not fire if there's any
whitespace between the E and the '. If by some chance there are
actually people out there using a type "e" with this syntax, they are
only in trouble if they wrote it with no space, and they can fix it by
adding a space. So I'm not very concerned.
Having said that, though, I'm agin back-porting this. We don't
back-patch feature additions, and this can hardly be described as
a bug fix.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Klint Gore | 2005-08-11 04:26:58 | Re: EnterpriseDB mentioned in eweek, and... |
Previous Message | Tom Lane | 2005-08-11 04:10:33 | Re: Index not being used unless enable_seqscan=false |