| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | uwcssa <uwcssa(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: un-vacuum? |
| Date: | 2006-01-19 21:58:31 |
| Message-ID: | 20060119215831.GA15442@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 19, 2006 at 03:54:33PM -0500, uwcssa wrote:
> I want to do this for repeating some experiment results, not for
> tuning the db (pretty much like using an old machine to find
> performance difference for an algorithm). so if i have a way
> of knowing which tables are storing the statistics, i guess i can
> delete all from that table to archieve this.
pg_statistic stores statistics. I think it's safe to delete rows,
but you might want to wait for one of the developers to comment
before mucking around with the stored values, especially if you're
not familiar with reading the pg_stats view.
http://www.postgresql.org/docs/8.1/interactive/catalog-pg-statistic.html
--
Michael Fuhr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-19 22:03:20 | Cache-flush stress testing |
| Previous Message | Bruce Momjian | 2006-01-19 21:56:17 | Re: [PATCH] Better way to check for getaddrinfo function. |