From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | tab completion of IMPORT FOREIGN SCHEMA |
Date: | 2020-08-09 15:46:42 |
Message-ID: | CAMkU=1wr7Roj41q-XiJs=Uyc2xCmHhcGGy7J-peJQK-e+w=ghw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I use IMPORT FOREIGN SCHEMA a bit to set up systems for testing. But not
enough that I can ever remember whether INTO or FROM SERVER comes first in
the syntax.
Here is an improvement to the tab completion, so I don't have to keep
looking it up in the docs.
It accidentally (even before this patch) completes "IMPORT FOREIGN SCHEMA"
with a list of local schemas. This is probably wrong, but I find this
convenient as I often do this in a loop-back setup where the list of
foreign schema would be the same as the local ones. So I don't countermand
that behavior here.
Cheers,
Jeff
Attachment | Content-Type | Size |
---|---|---|
foreign_schema_tab_complete.patch | application/octet-stream | 854 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-08-09 16:33:43 | Re: tab completion of IMPORT FOREIGN SCHEMA |
Previous Message | Thomas Munro | 2020-08-09 11:48:33 | Optimising latch signals |