Re: BUG #6624: Tab completion of identifier containing single backslash triggers warnings - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #6624: Tab completion of identifier containing single backslash triggers warnings
Date
Msg-id 20120502182110.GE21098@momjian.us
Whole thread Raw
In response to BUG #6624: Tab completion of identifier containing single backslash triggers warnings  (stuart@stuartbishop.net)
Responses Re: BUG #6624: Tab completion of identifier containing single backslash triggers warnings
List pgsql-bugs
On Wed, May 02, 2012 at 12:59:58PM +0000, stuart@stuartbishop.net wrote:
> The following bug has been logged on the website:
>
> Bug reference:      6624
> Logged by:          Stuart Bishop
> Email address:      stuart@stuartbishop.net
> PostgreSQL version: 9.1.3
> Operating system:   Ununtu
> Description:
>
> psql tab completion can emit WARNING messages if escape_string_warning is
> set to true. The trigger seems to be an identifier containing a single
> backslash.
>
> # 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 settings?

---------------------------------------------------------------------------


>
> (at this point, hit <TAB> to trigger completion)
>
> # drop sequence "\WARNING:  nonstandard use of \\ in a string literal
> LINE 1: ... substring(pg_catalog.quote_ident(c.relname),1,2)='"\\' AND ...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> WARNING:  nonstandard use of \\ in a string literal
> LINE 3: ...ing(pg_catalog.quote_ident(n.nspname) || '.',1,2)='"\\' AND ...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> WARNING:  nonstandard use of \\ in a string literal
> LINE 3: ...alog.quote_ident(nspname) || '.',1,2) = substring('"\\',1,pg...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> WARNING:  nonstandard use of \\ in a string literal
> LINE 5: ... || '.' || pg_catalog.quote_ident(c.relname),1,2)='"\\' AND ...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> WARNING:  nonstandard use of \\ in a string literal
> LINE 5: ...og.quote_ident(n.nspname) || '.',1,2) = substring('"\\',1,pg...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> WARNING:  nonstandard use of \\ in a string literal
> LINE 5: ...alog.quote_ident(nspname) || '.',1,2) = substring('"\\',1,pg...
>                                                              ^
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> foo" ;
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-bugs by date:

Previous
From: Matteo Beccati
Date:
Subject: Re: Errors on CREATE TABLE IF NOT EXISTS
Next
From: Josh Kupershmidt
Date:
Subject: Re: BUG #6624: Tab completion of identifier containing single backslash triggers warnings