st 8. 9. 2021 v 20:23 odesÃlatel Daniel Gustafsson <dan...@yesql.se> napsal:
> > On 8 Sep 2021, at 16:02, Pavel Stehule <pavel.steh...@gmail.com> wrote: > > > In the time when event triggers were introduced, managed services were > not too widely used like now. When we discussed this feature we thought > about environments when users have no superuser rights and have no > possibility to go to single mode. > > In situations where you don't have superuser access and cannot restart in > single user mode, none of the bypasses in this patch would help anyways. > If I remember well, it should be possible - you can set GUC in connection string, and this GUC is limited to the database owner. > I understand the motivation, but continuing on even in the face of an > ereport(ERROR.. ) in the hopes of being able to turn off buggy code seems > pretty unsafe at best. > I don't understand what you mean. I can disable the logon trigger by GUC. I cannot to enable an continue after an exception. Regards Pavel > > -- > Daniel Gustafsson https://vmware.com/ > >
