From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | "Erik Jones" <erik(at)myemma(dot)com> |
Cc: | "Dawid Kuroczko" <qnex42(at)gmail(dot)com>, "pgsql-general General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Trigger to run @ connection time? |
Date: | 2008-03-14 15:36:20 |
Message-ID: | e51f66da0803140836s4d380363l5f432f3f1ce1977d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/14/08, Erik Jones <erik(at)myemma(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2008-03-14 15:37:47 | Re: LOCK TABLE HELP |
Previous Message | Richard Huxton | 2008-03-14 15:27:01 | Re: LOCK TABLE HELP |