| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [SQL] 7.3 analyze & vacuum analyze problem |
| Date: | 2003-04-30 16:03:38 |
| Message-ID: | 200304300902.37985.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance pgsql-sql |
Achilleus,
> i think i have an issue regarding the statistics that
> a) (plain) ANALYZE status and
> b) VACUUM ANALYZE status
> produce.
It's perfectly normal for a query to run faster after a VACUUM ANALYZE than
after an ANALYZE ... after all, you just vacuumed it, didn't you?
If you're demonstrating some other kind of behavioural difference, then please
post the results of EXPLAIN ANALYZE for the two examples.
Oh, and we should probably shift this discussion to the PGSQL-PERFORMANCE
list.
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Luc Lachance | 2003-04-30 16:23:11 | Re: Why LIMIT after scanning the table? |
| Previous Message | Peter Darley | 2003-04-30 15:09:12 | Re: Query Plan far worse in 7.3.2 than 7.2.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Diehl, Jeffrey | 2003-04-30 16:34:40 | Like search performance. |
| Previous Message | Peter Darley | 2003-04-30 15:09:12 | Re: Query Plan far worse in 7.3.2 than 7.2.1 |