Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f52Ex7E32861 for ; Sat, 2 Jun 2001 10:59:07 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f52Ex0R11886; Sat, 2 Jun 2001 10:59:00 -0400 (EDT) To: Larry Rosenman cc: PostgreSQL SQL List Subject: Re: trying to summarize into a new table by time... In-reply-to: <20010602094435.A1773@lerami.lerctr.org> References: <20010602094435.A1773@lerami.lerctr.org> Comments: In-reply-to Larry Rosenman message dated "Sat, 02 Jun 2001 09:44:35 -0500" Date: Sat, 02 Jun 2001 10:58:59 -0400 Message-ID: <11883.991493939@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/16 X-Sequence-Number: 3219 > One more question, will the sum() on a bigint column cast to float > happen in floating point? Yes. You don't really need that though. These days there are only two flavors of sum(): float8 accumulator (for float8 and float4 inputs) and numeric accumulator (for everything else). You don't need to worry about overflow anymore. float8 is faster if you don't mind loss of precision... regards, tom lane