Skip site navigation (1) Skip section navigation (2)

Re: Per-function search_path => per-function GUC settings

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Per-function search_path => per-function GUC settings
Date: 2007-09-02 18:03:42
Message-ID: 1188756222.4144.56.camel@jdavis (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 2007-09-01 at 15:03 -0400, Tom Lane wrote:
> > ALTER FUNCTION func(args) SET var TO CURRENT;
> 
> Hmmm ... that's certainly do-able, though I'm not sure how much it helps
> the use-case you suggest.  The search path still has to be set at the
> top of the module script, no?

It gives some better options for module authors and people installing
those modules:

1. Set it at the top of the file, in one place

2. Connect as the user whose schema you want to install into, i.e.:
$ psql my_db jdavis < module_install.sql

3. prepend the "SET search_path=foo" to the input of psql, i.e.:
$ echo "SET search_path=foo;" | cat module_install.sql | psql my_db
..or
$ psql my_db
=> SET search_path=foo;
=> \i module_install.sql

Regards,
	Jeff Davis


In response to

pgsql-hackers by date

Next:From: Kenneth MarshallDate: 2007-09-02 18:04:04
Subject: Hash index todo list item
Previous:From: Jeff DavisDate: 2007-09-02 17:54:52
Subject: Re: Per-function search_path => per-function GUC settings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group