From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
---|---|
To: | Vik Reykja <vikreykja(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7612: Wrong result with join between two values () set |
Date: | 2012-10-18 16:03:05 |
Message-ID: | CAK-MWwR2AY=12a797czPLQuW=EDAuRi-fB8fK=WZoe+fMm9oUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 10/19/12, Vik Reykja <vikreykja(at)gmail(dot)com> wrote:
> On Thu, Oct 18, 2012 at 5:40 PM, <maxim(dot)boguk(at)gmail(dot)com> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 7612
>> Logged by: Maxim Boguk
>> Email address: maxim(dot)boguk(at)gmail(dot)com
>> PostgreSQL version: 9.2.1
>> Operating system: Linux
>> Description:
>>
>> Join between two values() set could produce wrong results:
>>
>
> This is not a bug; your test case produces correct results.
>
> Your VALUES clauses are producing one row with two columns each called
> "val" and "column2". You are joining on val and so when you switch the
> values to put 2 in different columns, no results are found.
>
> Is it possible you didn't intend to put the parentheses immediately
> following the VALUES keyword? I think that is the case because your
> parentheses around the numbers are superfluous.
Oops sorry for noise.
I should be more careful.
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2012-10-18 16:48:31 | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |
Previous Message | Vik Reykja | 2012-10-18 15:58:30 | Re: BUG #7612: Wrong result with join between two values () set |