Re: logical replication worker can't find postgis function - Mailing list pgsql-general

From Willy-Bas Loos
Subject Re: logical replication worker can't find postgis function
Date
Msg-id CAHnozTj+sGSsfGHUn-a0p2fN4-ov4yri9dPHgkBAk5972btE-Q@mail.gmail.com
Whole thread Raw
In response to Re: logical replication worker can't find postgis function  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: logical replication worker can't find postgis function  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
On Fri, Apr 22, 2022 at 3:20 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:

The trigger function is bad and dangerous, because it relies on the current setting of "search_path".

You notice that with logical replication, because "search_path" is empty to avoid security problems.

Thanks a lot!
Do you mean that all trigger functions are bad and dangerous, or just mine?
Do you have any suggestions for an alternative?

Cheers,
--
Willy-Bas Loos

pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: logical replication worker can't find postgis function
Next
From: Laurenz Albe
Date:
Subject: Re: logical replication worker can't find postgis function