Re: logical replication worker can't find postgis function

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: logical replication worker can't find postgis function
Date: 2022-04-22 13:26:37
Message-ID: CAHnozTj+sGSsfGHUn-a0p2fN4-ov4yri9dPHgkBAk5972btE-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 22, 2022 at 3:20 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2022-04-22 13:39:33 Re: logical replication worker can't find postgis function
Previous Message Laurenz Albe 2022-04-22 13:20:41 Re: logical replication worker can't find postgis function