From: | "Glenn Wiorek" <gwiorek(at)jmlafferty(dot)com> |
---|---|
To: | "Claudia D'amato" <claudia(dot)damato(at)allaxia(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres respond after toomany times to a query view |
Date: | 2003-12-22 16:54:30 |
Message-ID: | 012201c3c8ac$44c6b870$143264c8@jmlafferty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Postgres respond after toomany times to a query viewIt would help us to help you if you posted the view, tables involved and indexes on those table. Also things like some of the postgresql.conf parameters would help. Things like "effective_cache_size", "sort_mem". Also how often the tables in the views are update and how often you vacuum analyze will have a big impact on performance.
----- Original Message -----
From: Claudia D'amato
To: pgsql-hackers(at)postgresql(dot)org
Sent: Tuesday, December 16, 2003 3:15 AM
Subject: [HACKERS] Postgres respond after toomany times to a query view
Hi, I developing a program using postgres and linux like operating system. My problem is this:
I have a quite complicated view with roughly 10000 record. When I execute a simple query like this
"select * from myview"
postgres respond after 50 - 55 minutes roughly. I hope that someone can help me with some suggestion about reason of this behavior and some solution to reduce time ti have results. Thank you for your attentions and I hope to receive some feedback as soon as possible
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-12-22 17:06:43 | Re: FEATURE REQUEST: let arrays support null values. |
Previous Message | Andreas Pflug | 2003-12-22 16:18:04 | Re: cascading column drop to index predicates |