| From: | "Massa, Harald Armin" <chef(at)ghum(dot)de> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Gabriel Dinis <gabriel(dot)dinis(at)vigiesolutions(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PHP Web Auditing and Authorization |
| Date: | 2010-11-03 15:06:42 |
| Message-ID: | AANLkTimFok2yMV7C3AJBUGpFP4+i6Zz4sp==epYVuPsB@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill,
>
>
> We got this same kind of thing working by using PostgreSQL env variables.
> First, set custom_variable_classes in your postgresql.conf. You can then
> use the SET command to set variables of that class, and use them in your
> functions:
>
> that is an interesting hack. Just googled up
http://developer.postgresql.org/pgdocs/postgres/runtime-config-custom.html
and now I am wondering, where did you get your confidence that those
variables are bound to sessions and NOT bound to server instances? My
reading of that documentation let me stay in the assumption, those variables
are the same across server instances....
Harald
--
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
Amtsgericht Stuttgart, HRB 734971
-
persuadere.
et programmare
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2010-11-03 15:16:13 | Re: PHP Web Auditing and Authorization |
| Previous Message | Bill Moran | 2010-11-03 15:00:36 | Re: PHP Web Auditing and Authorization |