On Sat, Apr 23, 2011 at 12:24 PM, Robert Haas wrote:
> One thing to watch is the size of the filesystem cache. Generally as the
> system comes under memory pressure you will see the cache shrink. Not sure
> what is happening on your system, but typically when it gets down to some
> minimal siz
This is a good one :)
Here is a "brief" description of our issue(Postgres 9.0):
Tables:
main fact table:
Table "public.parent_fact"
Column|Type |
--+-+---
etime| date | not n
On Apr 17, 2011, at 11:30 AM, Phoenix Kiula wrote:
> Sorry, rejuvenating a thread that was basically unanswered.
>
> I closed the database for any kinds of access to focus on maintenance
> operations, killed all earlier processes so that my maintenance is the
> only stuff going on.
>
> REINDEX i
On Apr 18, 2011, at 1:13 PM, Uwe Bartels wrote:
> Hi Robert,
>
> thanks for your answer.
> the aggregate function I was talking about is the function I need to use for
> the non-group by columns like min() in my example.
> There are of course several function to choose from, and I wanted to know
On Apr 22, 2011, at 2:22 PM, Tory M Blue wrote:
> Thanks David and I have and in fact I do see spikes that would cause
> my system to run out of memory, but one thing I'm struggling with is
> my system always runs at the limit. It's the nature of linux to take
> all the memory and manage it.
One
On Apr 19, 2011, at 9:50 PM, Josh Berkus wrote:
> For example, on very large tables I've been known to set
> analyze_scale_factor to 0 and analyze_threshold to 5000.
Huh? Why?
>
...Robert
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your su
On Apr 18, 2011, at 6:08 PM, Stefan Keller wrote:
> I browsed the faq and looked at PostgreSQL performance books but I
> could not find the obvious:
> How to configure a read-only database server?
>
> I have a single-disk virtual Linux system and a read-only dataset
> which is exposed to internet
Willy-Bas Loos wrote:
>Hi,
>
>I'm using PostgreSQL 8.4 (and also 8.3).
>
>A partial index like this:
>CREATE INDEX table2_field1_idx
> ON table2 (field1)
> WHERE NOT field1 ISNULL;
>
>Will not be used when select one record from 100K records:
>
>explain select * from table2 where field1 = 2569
