Received: from sitraka.com (keeper2.klgroup.com [199.246.30.33]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5LJRLa36489 for ; Thu, 21 Jun 2001 15:27:22 -0400 (EDT) (envelope-from msherman@projectile.ca) Received: from rdmarcs (rd-marcs.sitraka.com [10.1.60.48]) by sitraka.com (8.8.8/8.8.4) with SMTP id PAA29150; Thu, 21 Jun 2001 15:27:03 -0400 (EDT) From: "Marc Sherman" To: "Mark Hamby" , "pgsql-sql List" Subject: RE: Select most recent record? Date: Thu, 21 Jun 2001 15:27:03 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200106/341 X-Sequence-Number: 3628 From: Mark Hamby [mailto:mark@archer.leavenworth.army.mil] > > Marc, > Did you ever get your problem solved to your satisfaction? > We have a very simular problem with a historical database > containing typically 5K id and updates to data every few > seconds. We tried unsuccessfully to optimize queries > such as those already suggested to you. We found the best > means to quickly query the data valid at any given time was > to: [snip] By adding an index, I was able to get the performance of the query within a reasonable threshold; it's still slow, but acceptable. I'll bear your suggestion in mind for next time I run into this kind of problem, though, if my sol'n can't handle the data. Thanks, - Marc