Re: IF (NOT) EXISTS in psql-completion - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: IF (NOT) EXISTS in psql-completion
Date
Msg-id 20161115.202642.194454658.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: IF (NOT) EXISTS in psql-completion  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: IF (NOT) EXISTS in psql-completion  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Hello, I rebased this patch on the current master.

At Mon, 31 Oct 2016 10:15:48 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote in
<20161031.101548.162143279.horiguchi.kyotaro@lab.ntt.co.jp>
> Anyway, I fixed space issues and addressed the
> COMPLETE_WITH_QUERY()'s almost unused parameter problem. And
> tried to write a README files.

tab-complete.c have gotten some improvements after this time.

577f0bdd2b8904cbdfde6c98f4bda6fd93a05ffc psql: Tab completion for renaming enum values.
927d7bb6b120a2ca09a164898f887eb850b7a329 Improve tab completion for CREATE TRIGGER.
1d15d0db50a5f39ab69c1fe60f2d5dcc7e2ddb9c psql: Tab-complete LOCK [TABLE] ... IN {ACCESS|ROW|SHARE}.

The attached patchset is rebsaed on the master including these
patches.

regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous execution
Next
From: Amit Kapila
Date:
Subject: Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows