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 e67IDOW55178; Fri, 7 Jul 2000 14:13:25 -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 OAA11094; Fri, 7 Jul 2000 14:12:34 -0400 (EDT) To: "Robert B. Easter" cc: Chris Bitmead , pgsql-bugs@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Re: [HACKERS] Re: [SQL] MAX() of 0 records. In-reply-to: <0007071258480C.01354@comptechnews> References: <396535EF.8132CF80@opentec.com.au> <3965F8A6.3322C001@bitmead.com> <10551.962987714@sss.pgh.pa.us> <0007071258480C.01354@comptechnews> Comments: In-reply-to "Robert B. Easter" message dated "Fri, 07 Jul 2000 12:53:27 -0400" Date: Fri, 07 Jul 2000 14:12:34 -0400 Message-ID: <11091.962993554@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/55 "Robert B. Easter" writes: > If you use min(x) or max(x) frequently, isn't it best to make a > trigger that intercepts x on insert and update, then check it and > store it somewhere rather than scanning for it everytime? I believe that's exactly what the original questioner is trying to do... regards, tom lane