From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
---|---|
To: | Kirk Wolak <wolakk(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: psql suggestion "select <tab>" offers nothing, can we get functions like "\df <tab>" |
Date: | 2025-04-07 16:55:37 |
Message-ID: | CALdSSPiCUB-pgALt6oWTngYcKAUD_J9c=u-9JJtGQB_E6gvtxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 4 Apr 2025, 16:41 Kirill Reshke, <reshkekirill(at)gmail(dot)com> wrote:
> On Thu, 3 Apr 2025 at 20:07, Kirk Wolak <wolakk(at)gmail(dot)com> wrote:
> > Worse, "select pg_stat_st<tab>" has no clue. I was looking for ...
> _reset
> >
> > It's not that difficult to add, I am suggesting that we use the same
> logic as \df at that point?
>
> Is not so simple here, because we have to try to complete this query
> with all attributes and functions, and there can be just too many
> different attname in the database. For example, with 100.000 tables
> you probably should wait for more than one second for a psql
> background query to complete (and you cannot cancel it too!). So this
> is very questionable if this feature is worth it.
>
> --
> Best regards,
> Kirill Reshke
>
Maybe we can tab-complete here if prefix matches pg_% ? Does that makes
good use case?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-04-07 17:05:43 | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Previous Message | Kirill Reshke | 2025-04-07 16:55:10 | Re: speedup COPY TO for partitioned table. |