On Thu, May 10, 2012 at 9:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, May 2, 2012 at 6:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The only way we could suppress such warnings would be if we made
tab-complete.c use E'' strings for literals
Robert Haas robertmh...@gmail.com writes:
On Wed, May 2, 2012 at 6:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The only way we could suppress such warnings would be if we made
tab-complete.c use E'' strings for literals containing name prefixes;
which is perhaps doable but it would mean having
On Wed, May 2, 2012 at 6:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The only way we could suppress such warnings would be if we made
tab-complete.c use E'' strings for literals containing name prefixes;
which is perhaps doable but it would mean having tab-complete.c roll
its own string escaping
The following bug has been logged on the website:
Bug reference: 6624
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.3
Operating system: Ununtu
Description:
psql tab completion can emit WARNING messages if
On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote:
The following bug has been logged on the website:
Bug reference: 6624
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.3
Operating system: Ununtu
On Wed, May 2, 2012 at 11:21 AM, Bruce Momjian br...@momjian.us wrote:
On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote:
# CREATE SEQUENCE \foo;
CREATE SEQUENCE
# \ds \
I am unable to reproduce this failure on my copy of 9.1.3. Have you
perhaps changed any server
Josh Kupershmidt schmi...@gmail.com writes:
On Wed, May 2, 2012 at 11:21 AM, Bruce Momjian br...@momjian.us wrote:
On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote:
# CREATE SEQUENCE \foo;
CREATE SEQUENCE
# \ds \
I am unable to reproduce this failure on my copy of
On Thu, May 3, 2012 at 5:29 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I'm inclined to think that if we got this far without complaint, there's
not a lot of point in writing new string-escaping support to solve what
is now a legacy problem.
I'm fine with that - I wasn't even sure if I should
