Re: [HACKERS] "CANNOT EXTEND" - - Mailing list pgsql-hackers

From D'Arcy" "J.M." Cain
Subject Re: [HACKERS] "CANNOT EXTEND" -
Date
Msg-id m10N0rH-0000cFC@druid.net
Whole thread Raw
In response to Re: [HACKERS] "CANNOT EXTEND" -  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Thus spake Bruce Momjian
> > template1=> SELECT oid from pg_database where datname = 'template1';
> > pqReadData() -- backend closed the channel unexpectedly.
> >         This probably means the backend terminated abnormally before
> 
> Can someone suggest why this would be happening?  The SELECT looks
> pretty simple.

It works for me but I have the same thing happening on a database
where I do the following.
 SELECT * INTO TABLE tempset FROM trash WHERE "Shape" ~* 'Prow' ;

The tempset table doesn't exist and trash is just a table that the
user is trying to grab a subselect from.  I don't know if there is
a connection here but it brought to mind a question I have been meaning
to ask, how do I read the pg_log file?  I can't seem to find anything
that reads this.  Also, what sort of stuff gets put into that log?

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Re: Developers Globe (FINAL)
Next
From: Clark Evans
Date:
Subject: Associative Operators? (Was: Re: [NOVICE] Out of frying pan, into fire)