Re: Please consider removing "select count(*)..."

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Yurgis Baykshtis" <ybaykshtis(at)aurigin(dot)com>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Please consider removing "select count(*)..."
Date: 2003-05-23 19:46:46
Message-ID: 03AF4E498C591348A42FC93DEA9661B825A210@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Yurgis Baykshtis [mailto:ybaykshtis(at)aurigin(dot)com]
> Sent: 23 May 2003 19:46
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Please consider removing "select
> count(*)..."
>
>
> In both pgAdmin 2 and 3, whenever I click on a table node in
> the object tree, for a table with relatively big number of
> rows, it's taking a very long time to update the property
> panel (up to a few minutes with very high CPU load by the
> postgres process) making practically impossible usage of the
> tool. The reason is in the "select count(*)" query pgAdmin
> use to get table row count.
> I am not sure whether there is another way to count table
> rows in Postgres, but I see it does not like 'select
> count(*)' much for large tables.
>
> I just commented out this query for myself forcing row count
> field to be always zero and it works just fine for me.

Hi Yurgis,

I've now added an option for this to the pgAdmin III CVS.

Regards, Dave.

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Yurgis Baykshtis 2003-05-23 20:26:43 Re: Please consider removing "select count(*)..."
Previous Message Dave Page 2003-05-23 19:08:23 Re: Please consider removing "select count(*)..."