Re: question on diagnostics - Mailing list pgsql-sql

From Tom Lane
Subject Re: question on diagnostics
Date
Msg-id 2669.960883529@sss.pgh.pa.us
Whole thread Raw
In response to Re: question on diagnostics  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-sql
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I can confirm this is still a bug.

Yeah, it's a parser problem.  I punted it in Lockhart's direction, but
he's been out of town...
        regards, tom lane


>>>>>> oh, btw this select refused to use an SQL natural join among the 3
>>>>>> relations - the server gives up and disconnects without warning.
>>>> 
>>>> That sounds like a garden-variety bug.  I'd be willing to look at it
>>>> if I had a complete example to follow, but I don't want to try to
>>>> reverse-engineer your table definitions...
>> 
>> a join with 3 tables never seems to work:
>> 
>> test=# create table a(a int);
>> CREATE
>> test=# create table b(a int);
>> CREATE
>> test=# create table c(a int);
>> CREATE
>> test=# insert into a values (1);
>> INSERT 23734 1
>> test=# insert into b values (1);
>> INSERT 23744 1
>> test=# insert into c values (1);
>> INSERT 23736 1
>> test=# select * 
>> test-# from a, b, c
>> test-# where a.a = b.a AND
>> test-#       b.a = c.a;
>> a | a | a 
>> ---+---+---
>> 1 | 1 | 1
>> (1 row)
>> test=# select * from a natural inner join b natural inner join c;
>> pqReadData() -- backend closed the channel unexpectedly.
>> This probably means the backend terminated abnormally
>> before or while processing the request.
>> The connection to the server was lost. Attempting reset: Failed.


pgsql-sql by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: question on diagnostics
Next
From: JanWieck@t-online.de (Jan Wieck)
Date:
Subject: Re: sql foregein key