pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Alexander H. Iliev <iliev@nimbus.dartmouth.edu>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: question on diagnostics
Date: Mon, 2 Oct 2000 00:17:13 -0400 (EDT)
Message-ID: <200010020417.AAA17102@candle.pha.pa.us> (raw)
In-Reply-To: <200006010507.BAA22920@nimbus.dartmouth.edu>

I can confirm that this is now fixed, and will appear in 7.1 when it is
released.

test=> select * from a natural inner join b natural inner join c;
 a 
---
 1
(1 row)


> > > 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.
> 
> 
> alex
> 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (7+ messages)

Message-ID: <200010020417.AAA17102@candle.pha.pa.us>
Permalink:  ../200010020417.AAA17102@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200010020417.AAA17102@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, iliev@nimbus.dartmouth.edu, tgl@sss.pgh.pa.us
  Subject: Re: question on diagnostics
  In-Reply-To: <200010020417.AAA17102@candle.pha.pa.us>
  References: <200006010507.BAA22920@nimbus.dartmouth.edu> <200010020417.AAA17102@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox