OK thanks for the help, have a nice weekend!
On Fri, Apr 22, 2022 at 3:39 PM Laurenz Albe
wrote:
> On Fri, 2022-04-22 at 15:26 +0200, Willy-Bas Loos wrote:
> > On Fri, Apr 22, 2022 at 3:20 PM Laurenz Albe
> wrote:
> > >
> > > The trigger function is bad and dangerous, because it relies on the
>
On Fri, 2022-04-22 at 15:26 +0200, Willy-Bas Loos wrote:
> On Fri, Apr 22, 2022 at 3:20 PM Laurenz Albe 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
On Fri, Apr 22, 2022 at 3:20 PM Laurenz Albe
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 t
On Fri, 2022-04-22 at 13:25 +0200, Willy-Bas Loos wrote:
> I'm using logical replication on postgresql 13. On the subscriber, there's a
> trigger on a table that calculates the area of the geometry that's in another
> column.
> I enabled the trigger with
> ALTER TABLE atable ENABLE ALWAYS TRIGG
Hi!
I'm using logical replication on postgresql 13. On the subscriber, there's
a trigger on a table that calculates the area of the geometry that's in
another column.
I enabled the trigger with
ALTER TABLE atable ENABLE ALWAYS TRIGGER atrigger;
But the logical replication worker can't find st_are
