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:03:57 |
Message-ID: | 1919.1135296237@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> 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.
This is really entirely irrelevant to Greg's complaint. To respond to
that, you'd have to modify the behavior of SHOW.
Actually, it seems that this exposes a bug in the search_path code: if
I wrote what you wrote, I'd really expect that it refers to a schema
named exactly $user --- the quoting ought to suppress the substitution,
one would think. Not sure how hard or easy that might be to implement
though ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2005-12-23 00:05:10 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
Previous Message | Bruce Momjian | 2005-12-22 23:57:19 | Re: Disparity in search_path SHOW and SET |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-23 00:12:06 | Re: Disparity in search_path SHOW and SET |
Previous Message | Bruce Momjian | 2005-12-22 23:57:19 | Re: Disparity in search_path SHOW and SET |