Message-ID: <1a884667-8474-dd01-d55f-1135724912f5@cloud.gatewaynet.com>
Date: Mon, 9 Sep 2024 13:24:41 +0300
MIME-Version: 1.0
Subject: Re: postgresql FDW vs dblink for DDL
To: Adrian Klaver <adrian.klaver@aklaver.com>,
 "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <c150aec1-10e1-4004-b71f-6a87efcf8b37@cloud.gatewaynet.com>
 <f54de1ef-7c11-4289-9075-560d899d1295@aklaver.com>
Content-Language: en-US
From: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
In-Reply-To: <f54de1ef-7c11-4289-9075-560d899d1295@aklaver.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/1a884667-8474-dd01-d55f-1135724912f5%40cloud.gatewaynet.com>
Precedence: bulk


On 9/8/24 23:46, Adrian Klaver wrote:
> On 9/8/24 13:04, Achilleas Mantzios wrote:
>> Hi
>>
>> for remote DDL execution (such as CREATE TABLE) is dblink my only 
>> option?
>
> You will need to define in what context you are considering options.
>
> For instance you can do remote DDL operations by passing a command or 
> script via psql.

Thank you Adrian,

I was thinking of wrapping the DDL around a FUNCTION that will handle 
both the local and the (possibly various logical subscriptions), so that 
my programmers don't need to write extra scripts.

And the thing is that this creation via DDL is inside our design. 
Certain users create some backup tables of the public data in their own 
schema (via our app), then do some manipulations on the public data, 
then restore to the public or merge with the backups. When done, those 
backup tables are dropped. So the DDL is inside the app. And the 
question was if dblink is my only option, in the sense of doing this in 
a somewhat elegant manner. (and not resort to scripts, etc)

>
>>
>> thanks
>>
>>
>>
>>
>