| From: | Ron <ronljohnsonjr(at)gmail(dot)com> | 
|---|---|
| To: | Marcin Borkowski <mbork(at)mbork(dot)pl>, pgsql-general(at)lists(dot)postgresql(dot)org | 
| Subject: | Re: A few questions about foreign tables | 
| Date: | 2023-10-18 16:14:44 | 
| Message-ID: | 66971fc2-d49c-4c50-a8bb-a185fd543fa1@gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
And SELECT relnamespace::regnamespace::text, relname FROM pg_class WHERE 
relkind='f'; tells you all of the foreign tables.
Thus, this (untested) query generate all of the DROP FOREIGN TABLE statements:
SELECT format('DROP FOREIGN TABLE IF EXISTS %I.%I RESTRICT;'
               , relnamespace::regnamespace::text, relname)
FROM pg_class WHERE relkind='f'
ORDER BY relkind;
On 10/18/23 10:56, Laurenz Albe wrote:
> On Wed, 2023-10-18 at 10:24 +0200, Marcin Borkowski wrote:
>> How to revert the effect of "import foreign schema"?  Is just dropping
>> the imported tables enough?
> Running DROP FOREIGN TABLE ... for all imported tables is enough.
>
>> Also, how can I check the definitions (i.e., what tables on the server
>> they correspond to) of existing foreign tables?
> \d+ <table name>
>
>> (May I ask to be cc'd since I'm not subscribed to the list?)
> But please reply to the list.
>
> Yours,
> Laurenz Albe
>
>
-- 
Born in Arizona, moved to Babylonia.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-10-18 16:15:22 | Re: postgres keeps having blocks | 
| Previous Message | Laurenz Albe | 2023-10-18 15:56:45 | Re: A few questions about foreign tables |