Skip site navigation (1) Skip section navigation (2)

Re: SELECT LIMIT 1 VIEW Performance Issue

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: K C Lau <kclau60(at)netvigator(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: SELECT LIMIT 1 VIEW Performance Issue
Date: 2005-09-22 16:16:23
Message-ID: 1127405783.4145.113.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Thu, 2005-09-22 at 22:39 +0800, K C Lau wrote:
> >Is a 51ms query really such a problem for you?
> Unfortunately yes, as our target performance is in the high hundreds of 
> transactions per sec. And 51 ms is already the best case for a single 
> select, with everything cached in memory immediately after the same select 
> which took 390 ms on a quiet system.

If the current value is used so often, use two tables - one with a
current view only of the row maintained using UPDATE. Different
performance issues maybe, but at least not correlated subquery ones.

Best Regards, Simon Riggs

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2005-09-22 16:17:32
Subject: Re: Nested Loop trouble : Execution time increases more 1000 time (long)
Previous:From: Tom LaneDate: 2005-09-22 15:41:14
Subject: Re: SELECT LIMIT 1 VIEW Performance Issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group