Any way to pull the value of a config variable into a pl/pgsql variable?
> -----Original Message----- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: Friday, March 02, 2007 3:46 PM > To: David Fetter > Cc: Adam Rich; pgsql-general@postgresql.org > Subject: Re: [GENERAL] Custom session variables? > > > David Fetter <[EMAIL PROTECTED]> 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 > ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
