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

Re: Disparity in search_path SHOW and SET

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Disparity in search_path SHOW and SET
Date: 2005-12-23 00:26:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Uh, SHOW does show the quotes:

> 	test=> show search_path;
> 	  search_path
> 	----------------
> 	 "$user",public
> 	(1 row)

Hmm ... you're right, it does, so the current default is actually a
value that you can't get into the variable by a normal SET.
Interesting.  (We are doing the "smart" stuff during SET not SHOW,
it appears.)

regression=# show search_path ;
(1 row)

regression=# set search_path = '$user',public;
regression=# show search_path ;
 "$user", public
(1 row)

Given that, I agree with changing the default string.  It should look
the same as a value that you could actually assign ...

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2005-12-23 00:29:29
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Ashok AgrawalDate: 2005-12-23 00:25:53
Subject: Re: Oracle PL/SQL Anonymous block equivalent in postgres

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-12-23 00:38:28
Subject: Re: Disparity in search_path SHOW and SET
Previous:From: Bruce MomjianDate: 2005-12-23 00:14:49
Subject: Re: Trouble building 8.1.1 on Tru64 UNIX 5.1

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