Re: psql completion bugs with access methods

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql completion bugs with access methods
Date: 2019-06-01 19:25:29
Message-ID: 20190601192529.sdl6z4y7gs4nii6u@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I'm not sure I understand starting 10 threads about approximately the
same topic. That seems purely confusing.

On 2019-06-01 15:10:07 -0400, Michael Paquier wrote:
> I have bumped into a couple of issues with psql completion for access
> methods:
> 1) CREATE INDEX USING suggests both index and table AMs.

Let's fix that.

> 2) CREATE TABLE USING has no completion support, USING not being
> included in the completion, and the follow-up table AMs are missing as
> well.
> 3) CREATE ACCESS METHOD TYPE suggests only INDEX.

I don't think these are bugs. I'm fine with adding those for 12, but I
don't think it's needed.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-06-01 19:35:35 Re: Doc fix on information_schema.views
Previous Message Andres Freund 2019-06-01 19:22:10 Re: Table AM callbacks referring to heap in declarations (+typos)