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

Re: Disparity in search_path SHOW and SET

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
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 02:08:13
Message-ID: 43AB5C0D.9050209@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> Agreed.  I have gotten confused on how to set $user in the past.  I have
> developed the following patch that sets the default with the double
> quotes around it, and it works fine.  The patch also contains updated
> documentation.

Just be careful about pg_dump's special handling of search_path in user 
and db variables...

Make sure you haven't broken it.

Chris


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-12-23 04:13:07
Subject: Re: [pgadmin-hackers] Client-side password encryption
Previous:From: Christopher Kings-LynneDate: 2005-12-23 02:06:24
Subject: Re: [pgadmin-hackers] Client-side password encryption

pgsql-patches by date

Next:From: Tom LaneDate: 2005-12-23 04:38:26
Subject: Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding
Previous:From: Bruce MomjianDate: 2005-12-23 02:04:40
Subject: Re: Disparity in search_path SHOW and SET

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