On 3/14/08, Erik Jones <[EMAIL PROTECTED]> wrote: > On Mar 14, 2008, at 7:17 AM, Marko Kreen wrote: > > To put it to core Postgres, it needs to be conceptually sane > > first, without needing ugly workarounds to avoid it bringing > > whole db down. > > > > I can see ATM only few ways: > > > > - Applies only to non-superusers. > > > > - Error from CONNECT trigger does not affect superuser. > > > > - Applies to database + role. Role could be also group of users. > > > > So you always have way do fix things, without hexediting in data > > dir... > > Another option: > > Does not fire at all in single-user mode. This would be covered by > "Applies to non-superusers" if that were there but, by itself, the > triggers would still fire for normal superuser connections.
Seems bit too hard - you may other db-s that work fine, why should those suffer? -- marko -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
