| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Several problems in tab-completions for SET/RESET |
| Date: | 2016-01-28 12:32:11 |
| Message-ID: | CAHGQGwFoPWQBdn0vMPKqKvSE=EDij1kMNHZ7cq=+2kg2AF1sdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I found that the following tab-completions for SET/RESET which
worked properly before doesn't work properly now in the master.
1. ALTER SYSTEM SET|RESET <tab> lists nothing.
2. ALTER DATABASE xxx SET <tab> lists nothing.
3. ALTER DATABASE xxx SET yyy <tab> lists nothing.
4. ALTER DATABASE xxx SET datestyle TO <tab> lists nothing.
Attached patch fixes those problems.
Regards,
--
Fujii Masao
| Attachment | Content-Type | Size |
|---|---|---|
| fix_tab_complete_for_set.patch | text/x-patch | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2016-01-28 12:36:58 | Re: Odd behavior in foreign table modification (Was: Re: Optimization for updating foreign tables in Postgres FDW) |
| Previous Message | Michael Paquier | 2016-01-28 12:24:02 | Re: Proposal:Use PGDLLEXPORT for libpq |