Re: Disparity in search_path SHOW and SET

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Disparity in search_path SHOW and SET
Date: 2005-12-20 17:30:07
Message-ID: 6b4948bc5f7c87d5526b1549746ffd47@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Well, sure, because you told it to. Why isn't the last parameter "false"?

Thanks. I knew I was overlooking something. I've obviously been staring at
the code too long. :) Still, would it make more sense for SHOW search_path
to return this:

"$user",public

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200512201227
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFDqD83vJuQZxSWSsgRAj1gAKDIRGqzD7zORJQwrxLM+oKWOiAPKgCg9/xK
OGZIoWEnLdw+Qi71lKbCg0g=
=0dBJ
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-12-20 17:44:35 Re: Disparity in search_path SHOW and SET
Previous Message Martin Pitt 2005-12-20 17:27:55 Re: horology regression test failure

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2005-12-20 17:37:57 Re: PLpgSQL: list of scalars as row for assign stmt, fore and fors stms
Previous Message Tom Lane 2005-12-20 17:21:20 Re: Disparity in search_path SHOW and SET