From: | brian <brian(at)zijn-digital(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Weird double single quote issue |
Date: | 2006-11-02 16:56:43 |
Message-ID: | 454A234B.1090900@zijn-digital.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Peter <peter(at)greatnowhere(dot)com> writes:
>
>>2. No. In fact I can replicate the problem on the same computer using
>>PgAdmin (connecting as two different users)
>>3. I can isolate the part but it does not help much. I'm even doing
>>RAISE NOTICE and printing out the actual SQL statement that is being
>>executed... and it's IDENTICAL for both users yet returns different
>>values. Executing exactly the same SQL statement from commandline
>>produces identical results for both users.
>
>
> It's really pretty hard to believe that the same function would work
> differently for two different users. I'm wondering if maybe the two
> users aren't executing the same function --- perhaps not the specific
> one you are looking at, but some other one it depends on. Do the
> users have different search_path settings?
>
I'm thinking that the data returned might be dependent upon the user. Is
this the case? And can any of those columns used in the proc be NULL?
Frankly, i couldn't read it very well (but then, i'm on my first cup of
coffee this morning), but i'm wondering if the problem lies somewhere in
between the dollar-quoting and coalesce().
brian
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Weber | 2006-11-02 17:12:25 | query takes 65 times longer if I add 1 column (explain attached) |
Previous Message | Tom Lane | 2006-11-02 16:44:04 | Re: lots of values for IN() clause |