Oleg,
> I just vacuumed and vacuumed analyzed my database. Now, I am trying
> to
> execute a view, which was perfectly working before, but it seems to
> be
> very slow. It was sitting there for 10 mins before I cancelled it.
> Usually it was taking on the order of 5 secs to execute the view.
> I just recreated the view, but the problem still persists.
> Here is what EXPLAIN tells me:
> EXPLAIN select * from progress_report;
> Subquery Scan progress_report (cost=16386.56..16386.56 rows=2
> width=128)
> -> Sort (cost=16386.56..16386.56 rows=2 width=128)
> -> Nested Loop (cost=16299.45..16386.55 rows=2 width=128)
>
> How can I "restore" the "before-the-vacuum" performance?
> thanks,
This is not normal. I suspect that you have something wrong with your
Postgres system configuration or your system in general.
Please post:
1. Your postgres version
2. Your platform (OS and version)
3. Your hardware statistics, including:Processor & RAMDisk space free on your root drive and postgres drive
4. The view definition
5. Row counts on all tables involved in the view, as well as whether
those tables have very large text fields or BLOBs.
6. Finally, check your Postgres log to see if VACUUM raised any errors,
and to see if selecting the view causes any errors.
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete
informationtechnology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small
businesses fax 621-2533 and non-profit organizations. San Francisco