Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e5D85gT57668 for ; Tue, 13 Jun 2000 04:05:42 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id EAA02672; Tue, 13 Jun 2000 04:05:29 -0400 (EDT) To: Bruce Momjian cc: "Alexander H. Iliev" , pgsql-sql@postgresql.org Subject: Re: question on diagnostics In-reply-to: <200006130801.EAA24703@candle.pha.pa.us> References: <200006130801.EAA24703@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 13 Jun 2000 04:01:41 -0400" Date: Tue, 13 Jun 2000 04:05:29 -0400 Message-ID: <2669.960883529@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/139 Bruce Momjian 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.