| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Mead <scottm(at)openscg(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalid search_path complaints |
| Date: | 2012-04-04 16:22:13 |
| Message-ID: | 28026.1333556533@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Scott Mead <scottm(at)openscg(dot)com> writes:
> On Wed, Apr 4, 2012 at 12:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, that's an interesting analogy. Are you arguing that we should
>> always accept any syntactically-valid search_path setting, no matter
>> whether the mentioned schemas exist? It wouldn't be hard to do that.
> I think we should always accept a syntactically valid search_path.
I could live with that.
>> The fun stuff comes in when you try to say "I want a warning in these
>> contexts but not those", because (a) the behavior you think you want
>> turns out to be pretty squishy, and (b) it's not always clear from the
>> implementation level what the context is.
> ISTM that just issuing a warning whenever you set the search_path (no
> matter which context) feels valid (and better than the above *nix
> behavior). I would personally be opposed to seeing it on login however.
You're getting squishy on me ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-04-04 16:22:19 | Re: patch: improve SLRU replacement algorithm |
| Previous Message | Tom Lane | 2012-04-04 16:18:32 | Re: Question regarding SSL code in backend and frontend |