Re: BUG #13655: Incorrect Syntax Error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13655: Incorrect Syntax Error
Date
Msg-id 13218.1443674688@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #13655: Incorrect Syntax Error  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: BUG #13655: Incorrect Syntax Error  (David <stormbyte@gmail.com>)
List pgsql-bugs
Haribabu Kommi <kommi.haribabu@gmail.com> writes:
> On Thu, Oct 1, 2015 at 11:56 AM, David G. Johnston
> <david.g.johnston@gmail.com> wrote:
>> On Wednesday, September 30, 2015, Haribabu Kommi <kommi.haribabu@gmail.com>
>> wrote:
>>> As I feel this is not a bug. psql has the tab complete feature with
>>> the help of readline library.
>>> Means it tries fill the command if the user provides the tab key as input.

>> Tab-completion should not interfere with script code provided
>> non-interactively on standard input, or in a script file loaded using -f or
>> \i

> Tab-completion doesn't change <TAB> characters if the file passed
> using -f or \i.

Yeah.  I could not reproduce the reported error when feeding the file
to psql using "-f file", "<file", or "\i file".  It is possible to get
it by pasting the given text into a terminal window, so that readline
can't tell that you didn't manually type the TAB.

Worth noting here is you can turn off readline with the -n option
to psql.  I've done that sometimes when there was a reason not to want
TAB to act as command-completion.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: BUG #13655: Incorrect Syntax Error
Next
From: swingi@gmail.com
Date:
Subject: BUG #13656: table inheritance, pg_dump emits same constraint for all inheritors causing errors