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

Re: Disparity in search_path SHOW and SET

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(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:38:28
Message-ID: 200512230038.jBN0cSu09861@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
OK, applied.  I have _not_ backpatched this.

---------------------------------------------------------------------------

Tom Lane wrote:
> 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 ;
>  search_path
> --------------
>  $user,public
> (1 row)
> 
> regression=# set search_path = '$user',public;
> SET
> regression=# show search_path ;
>    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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Qingqing ZhouDate: 2005-12-23 00:53:04
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Bruce MomjianDate: 2005-12-23 00:35:05
Subject: Re: Oracle PL/SQL Anonymous block equivalent in postgres

pgsql-patches by date

Next:From: Tatsuo IshiiDate: 2005-12-23 01:42:07
Subject: Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding
Previous:From: Tom LaneDate: 2005-12-23 00:26:36
Subject: Re: Disparity in search_path SHOW and SET

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