| From: | Francisco Reyes <lists(at)natserv(dot)com> |
|---|---|
| To: | Bill Gribble <grib(at)linuxdevel(dot)com> |
| Cc: | Gunther Schadow <gunther(at)aurora(dot)regenstrief(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Critical performance problems on large databases |
| Date: | 2002-04-19 16:15:12 |
| Message-ID: | 20020419121330.L76398-100000@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11 Apr 2002, Bill Gribble wrote:
> On Wed, 2002-04-10 at 17:39, Gunther Schadow wrote:
>
> Then the biggest slowdown is count(*), which we have to do in order to
> fake up the scrollbar (so we know what proportion of the data has been
> scrolled through). I have not completely foxed this yet. I want to
> keep a separate mini-table of how many records are in the big table and
> update it with a trigger (the table is mostly static). ATM, I just try
> hard to minimize the times I call count(*).
Dont' recall right now which table, but there is a table that has record
counts. It is accurate if you have done a vacuum full. Vacuum analyze only
gives you estimates, but that may be good enough for your needs.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2002-04-19 16:36:25 | Re: Troubleshooting cored dumps |
| Previous Message | Francisco Reyes | 2002-04-19 16:08:58 | Re: COPY performance |