From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
---|---|
To: | Ken Kato <katouknl(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Tab completion for GRANT MAINTAIN |
Date: | 2023-04-19 11:50:30 |
Message-ID: | a8ae0f8b-8ecb-a3f5-0c1b-bcb4bda1c80a@uni-muenster.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18.04.23 11:08, Ken Kato wrote:
> Hi hackers,
>
> I found that GRANT MAINTAIN is not tab-completed with ON, so here is a
> patch.
Hi,
the patch applies cleanly and now GRANT MAINTAIN tab-completes with ON.
For the sake of completeness I tested a whole statement:
postgres=# GRANT M<tab>
=> postgres=# GRANT MAINTAIN
postgres=# GRANT MAINTAIN <tab>
=> postgres=# GRANT MAINTAIN ON
postgres=# GRANT MAINTAIN ON t <tab>
=> postgres=# GRANT MAINTAIN ON t TO
postgres=# GRANT MAINTAIN ON t TO <tab><tab>
=>
CURRENT_ROLE pg_monitor pg_use_reserved_connections
CURRENT_USER pg_read_all_data pg_write_all_data
pg_checkpoint pg_read_all_settings pg_write_server_files
pg_create_subscription pg_read_all_stats postgres
pg_database_owner pg_read_server_files PUBLIC
pg_execute_server_program pg_signal_backend SESSION_USER
pg_maintain pg_stat_scan_tables
I've marked the CF entry as "ready for committer"
Best, Jim
From | Date | Subject | |
---|---|---|---|
Next Message | Ajit Awekar | 2023-04-19 11:52:32 | Memory leak in CachememoryContext |
Previous Message | vignesh C | 2023-04-19 11:05:18 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |