From: sathiya psql <sathiya.psql@gmail.com>
To: jose javier parra sanchez <jojapasa@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgresql is slow with larger table even it is in RAM
Date: Tue, 25 Mar 2008 14:12:53 +0530
Message-ID: <f966c2ee0803250142hae53ef4mfee4487d1fd052a2@mail.gmail.com> (raw)
In-Reply-To: <99f1636c0803250139g321329dbr7c640213e9132583@mail.gmail.com>
References: <f966c2ee0803250135h57ba1d5bs41f77616ae7186dc@mail.gmail.com>
<99f1636c0803250139g321329dbr7c640213e9132583@mail.gmail.com>
On Tue, Mar 25, 2008 at 2:09 PM, jose javier parra sanchez <
jojapasa@gmail.com> wrote:
> It's been said zillions of times on the maillist. Using a select
> count(*) in postgres is slow, and probably will be slow for a long
> time. So that function is not a good way to measure perfomance.
>
Yes, but if the data is in HDD then we can say this...
but now the data is in RAM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sathiya.psql@gmail.com, jojapasa@gmail.com
Subject: Re: postgresql is slow with larger table even it is in RAM
In-Reply-To: <f966c2ee0803250142hae53ef4mfee4487d1fd052a2@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox