Re: Making tab-complete.c easier to maintain - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Making tab-complete.c easier to maintain
Date
Msg-id CAEepm=1Oaq+L_6KCZ5o_hNn-=T93_LiK=_T1C9DcPzgXs4H84g@mail.gmail.com
Whole thread Raw
In response to Re: Making tab-complete.c easier to maintain  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Making tab-complete.c easier to maintain  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On Sat, Oct 24, 2015 at 6:19 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> On Sun, Oct 18, 2015 at 9:12 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> Thanks for taking a look at this!  The word count returned by
>> get_previous_words was incorrect.  Here is a corrected version.
>
> I haven't looked at v6 yet, but in v5:
>
> "set work_mem TO" completes to "NULL" not to "DEFAULT"
>
> line 2665 of the patched tab complete file,, should be "DEFAULT", not "NULL"
> as the completion string.  Looks like a simple copy and paste error.

Indeed.  Thanks.  Fixed in the attached.

--
Thomas Munro
http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [DESIGN] ParallelAppend
Next
From: Greg Stark
Date:
Subject: Re: Making tab-complete.c easier to maintain