Re: Options for Postgres FDW

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: PegoraroF10 <marcos(at)f10(dot)com(dot)br>, pgsql-general(at)postgresql(dot)org
Subject: Re: Options for Postgres FDW
Date: 2020-01-30 22:11:48
Message-ID: 9ca98015-fb73-f1e9-56b3-d6dc0f779a93@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/30/20 1:59 PM, PegoraroF10 wrote:
> I´m trying to insert/update some tables using FDW. I´m having problems when I
> want to use default values and triggers.
>
> For columns with default values, if I drop that column on foreign table
> definition is fine for inserts but I cannot use that column for
> updates/selects because it doesn´t exist on foreign table definition.

Don't drop it?

>
> For triggers, there is a way to define search_path for that
> server/connection ? Because suppose I´ve used "import foreign schema

?:
https://www.postgresql.org/docs/12/sql-alterrole.html
ALTER ROLE { role_specification | ALL } [ IN DATABASE database_name ]
SET configuration_parameter { TO | = } { value | DEFAULT }

> CustomerSchema", when I do some insert/update on any table of this schema,
> if that table calls a trigger which needs another table, that trigger
> doesn´t sees that table because it´s using pg_catalog schema. The only way
> to solve this is defining search_path when starting all triggers ?
>
>
>
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-01-30 22:16:51 Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Previous Message Adrian Klaver 2020-01-30 22:04:15 Re: Options for Postgres FDW