| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Adam Rich <adam(dot)r(at)sbcglobal(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Custom session variables? |
| Date: | 2007-03-02 21:45:30 |
| Message-ID: | 16931.1172871930@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Fetter <david(at)fetter(dot)org> writes:
> On Fri, Mar 02, 2007 at 01:53:28PM -0600, Adam Rich wrote:
>> Is there any way to define custom variables per session scope?
> You can have them in PL/Perl(U), PL/Tcl(U) and PL/PythonU and other
> such PLs, and you can create SQL accessors for them.
Another possibility is the "customized GUC options" route: you can take
advantage of the fact that the backend will let you set variables that
don't exist yet, if they are in a namespace that postgresql.conf says
is OK.
http://www.postgresql.org/docs/8.2/static/runtime-config-custom.html
This approach probably doesn't scale nicely to a whole lotta values,
but for a dozen or so strings it'd work well enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Rich | 2007-03-02 21:57:37 | Re: Custom session variables? |
| Previous Message | Joshua D. Drake | 2007-03-02 21:44:30 | Re: [HACKERS] WITH/RECURSIVE plans |