From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter <peter(at)greatnowhere(dot)com> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Weird double single quote issue |
Date: | 2006-11-02 16:21:51 |
Message-ID: | 17299.1162484511@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-11-02 16:23:09 | Re: lots of values for IN() clause |
Previous Message | Martijn van Oosterhout | 2006-11-02 16:20:26 | Re: lots of values for IN() clause |