| From: | Erik Jones <erik(at)myemma(dot)com> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(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 14:59:13 |
| Message-ID: | EA7F5C12-81DB-462C-A52A-6C4EB3319611@myemma.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2008-03-14 15:02:28 | Re: LOCK TABLE HELP |
| Previous Message | Erik Jones | 2008-03-14 14:52:35 | Re: postgre vs MySQL |