Re: [HACKERS] min() and max() causing aborts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] min() and max() causing aborts
Date: 1999-03-21 17:00:13
Message-ID: 7530.922035613@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> Are other people now seeing aggregate failure. If so, I will post the
> remainder of the patch that is still installed to see if removing that
> will help, thought the other part deals more with expressions than
> aggregates.

Yesterday evening (after you partially backed out that patch) I updated
and rebuilt and ran regression test. I didn't see any regress failures
involving aggregates, and a quick hand smoke-test of max and min looks
OK:

regression=> select max(f1) from float8_tbl;
max
---
0
(1 row)

regression=> select min(f1) from float8_tbl;
min
---------------------
-1.2345678901234e+200
(1 row)

There were a couple of other things broken yesterday, but they didn't
seem related to Michael's problem.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-03-21 18:51:38 Re: [HACKERS] discussion on proposed int8_ops patch
Previous Message Tom Lane 1999-03-21 15:55:11 Re: [HACKERS] Unary % operator is broken in current sources