Re: Making tab-complete.c easier to maintain

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making tab-complete.c easier to maintain
Date: 2015-10-19 03:58:00
Message-ID: CAMkU=1yt=Ed7+K4sUisdUkt-wDhGnxdkDqs_43uJvhJYFA56gQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 18, 2015 at 5:31 PM, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com
> wrote:

> Hi
>
> Here is a new version merging recent changes.
>

For reasons I do not understand, "SET work_mem " does not complete with
"TO".

But if I change:

else if (Matches2("SET", MatchAny))

to:

else if (TailMatches2("SET", MatchAny))

Then it does.

Cheers,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2015-10-19 04:12:29 Re: Making tab-complete.c easier to maintain
Previous Message Tom Lane 2015-10-19 03:16:52 Re: Why no CONSTANT for row variables in plpgsql?