I recompiled everything several time, did an initdb each time, reloaded my
database, and did a vacuum.  No I did not see anything in the postmaster log
file. 

I updated my cvs tree this morning.   And rebuild everything again.  I
deleted my data directory and in initdb followed by:

createdb mp
psql -e < mp.out			-- dump from 6.4.2
Connection to database 'postgres' failed.
FATAL 1:  Database postgres does not exist in pg_database

I cant even load data with the lastest set of changes.  There are no
messages in the postgres .log file or .err files.

There are still failures in the regression tests:

boolean .. ok
char .. ok
name .. ok
varchar .. ok
text .. ok
strings .. ok
int2 .. failed
int4 .. failed
int8 .. ok
oid .. ok
float4 .. ok
float8 .. failed
numerology .. ok
point .. ok
lseg .. ok
box .. ok
path .. ok
polygon .. ok
circle .. ok
geometry .. failed
timespan .. ok
datetime .. ok
reltime .. ok
abstime .. ok
tinterval .. ok
horology .. ok
inet .. ok
comments .. ok
opr_sanity .. ok
create_function_1 .. ok
create_type .. ok
create_table .. ok
create_function_2 .. ok
constraints .. ok
triggers .. failed
copy .. ok
create_misc .. ok
create_aggregate .. ok
create_operator .. ok
create_view .. ok
create_index .. ok
sanity_check .. ok
errors .. ok
select .. ok
select_into .. ok
select_distinct .. ok
select_distinct_on .. ok
select_implicit .. ok
select_having .. failed
subselect .. ok
union .. ok
case .. ok
join .. ok
aggregates .. failed
transactions .. ok
random .. ok
portals .. ok
misc .. failed
arrays .. ok
btree_index .. ok
hash_index .. ok
select_views .. ok
alter_table .. ok
portals_p2 .. ok
rules .. ok
limit .. ok
install_plpgsql .. ok
plpgsql .. ok
temp .. ok


	-----Original Message-----
	From:	Bruce Momjian [SMTP:maillist@candle.pha.pa.us]
	Sent:	Saturday, March 20, 1999 5:41 AM
	To:	Michael Davis
	Cc:	pgsql-hackers@postgreSQL.org
	Subject:	Re: [HACKERS] min() and max() causing aborts

	> I pulled the latest version of the source tree yesterday and
complied
	> PosgtreSQL 6.5.  The get the following error on any select
statement
	> containing min() and max():
	> 
	> mp=> select max(addressid) from addresses;
	> pqReadData() -- backend closed the channel unexpectedly.
	>         This probably means the backend terminated abnormally
before or
	> while processing the request.
	> We have lost the connection to the backend, so further processing
is
	> impossible.  Terminating.
	> 
	> 
	> I am running Red Hat 5.1.
	> 
	> FYI, I also noticed failures in the regressions tests for int2 and
int4 and
	> some others (int8 was okay).  I did not dig very deep into this
but the only
	> error I could see with int2 and int4 occurred when the value that
was being
	> inserted into the table was too large for the field.  For example,
inserting
	> 100000 into an int2 field.
	> 

	I recommend a clean compile and initdb to see if that fixes it.  Do
you
	see anything in the postmaster log file?

	-- 
	  Bruce Momjian                        |  http://www.op.net/~candle
	  maillist@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

Sat, 20 Mar 1999 15:29:37 -0600
Michael Davis <michael.davis@prevuenet.com>
RE: [HACKERS] min() and max() causing aborts
Fixed this morning at 8am EST.


> I recompiled everything several time, did an initdb each time, reloaded my
> database, and did a vacuum.  No I did not see anything in the postmaster log
> file. 
> 
> I updated my cvs tree this morning.   And rebuild everything again.  I
> deleted my data directory and in initdb followed by:
> 
> createdb mp
> psql -e < mp.out			-- dump from 6.4.2
> Connection to database 'postgres' failed.
> FATAL 1:  Database postgres does not exist in pg_database
> 
> I cant even load data with the lastest set of changes.  There are no
> messages in the postgres .log file or .err files.
> 
> There are still failures in the regression tests:
> 
> boolean .. ok
> char .. ok
> name .. ok
> varchar .. ok
> text .. ok
> strings .. ok
> int2 .. failed
> int4 .. failed
> int8 .. ok
> oid .. ok
> float4 .. ok
> float8 .. failed
> numerology .. ok
> point .. ok
> lseg .. ok
> box .. ok
> path .. ok
> polygon .. ok
> circle .. ok
> geometry .. failed
> timespan .. ok
> datetime .. ok
> reltime .. ok
> abstime .. ok
> tinterval .. ok
> horology .. ok
> inet .. ok
> comments .. ok
> opr_sanity .. ok
> create_function_1 .. ok
> create_type .. ok
> create_table .. ok
> create_function_2 .. ok
> constraints .. ok
> triggers .. failed
> copy .. ok
> create_misc .. ok
> create_aggregate .. ok
> create_operator .. ok
> create_view .. ok
> create_index .. ok
> sanity_check .. ok
> errors .. ok
> select .. ok
> select_into .. ok
> select_distinct .. ok
> select_distinct_on .. ok
> select_implicit .. ok
> select_having .. failed
> subselect .. ok
> union .. ok
> case .. ok
> join .. ok
> aggregates .. failed
> transactions .. ok
> random .. ok
> portals .. ok
> misc .. failed
> arrays .. ok
> btree_index .. ok
> hash_index .. ok
> select_views .. ok
> alter_table .. ok
> portals_p2 .. ok
> rules .. ok
> limit .. ok
> install_plpgsql .. ok
> plpgsql .. ok
> temp .. ok
> 
> 
> 	-----Original Message-----
> 	From:	Bruce Momjian [SMTP:maillist@candle.pha.pa.us]
> 	Sent:	Saturday, March 20, 1999 5:41 AM
> 	To:	Michael Davis
> 	Cc:	pgsql-hackers@postgreSQL.org
> 	Subject:	Re: [HACKERS] min() and max() causing aborts
> 
> 	> I pulled the latest version of the source tree yesterday and
> complied
> 	> PosgtreSQL 6.5.  The get the following error on any select
> statement
> 	> containing min() and max():
> 	> 
> 	> mp=> select max(addressid) from addresses;
> 	> pqReadData() -- backend closed the channel unexpectedly.
> 	>         This probably means the backend terminated abnormally
> before or
> 	> while processing the request.
> 	> We have lost the connection to the backend, so further processing
> is
> 	> impossible.  Terminating.
> 	> 
> 	> 
> 	> I am running Red Hat 5.1.
> 	> 
> 	> FYI, I also noticed failures in the regressions tests for int2 and
> int4 and
> 	> some others (int8 was okay).  I did not dig very deep into this
> but the only
> 	> error I could see with int2 and int4 occurred when the value that
> was being
> 	> inserted into the table was too large for the field.  For example,
> inserting
> 	> 100000 into an int2 field.
> 	> 
> 
> 	I recommend a clean compile and initdb to see if that fixes it.  Do
> you
> 	see anything in the postmaster log file?
> 
> 	-- 
> 	  Bruce Momjian                        |  http://www.op.net/~candle
> 	  maillist@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
> 
> 


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@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

Sat, 20 Mar 1999 20:16:52 -0500 (EST)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] min() and max() causing aborts