> do many of the statistical queries use the whole month's data?
> have you considered partitioning the log table by day? if you can
> reduce the number of rows involved in the table-scans by partitioning
> it'll be help performance.
>
I am summarising by hour, day, week and month. So I guess par
On 2012-06-06, Ben Carbery wrote:
> In the current environment I am given a single VHDD which I have not
> partitioned at all. The SAN performance is pretty good, but we have noticed
> slowdowns at various times.. The database does a lot of logging - constant
> small writes, with some probably in
On 06/06/2012 01:07 AM, Ben Carbery wrote:
The new server has a great deal more memory which I am hoping will
help (shared_buffers = 8GB, total RAM 20GB), but I am looking at what
might be optimal for the storage configuration. From looking at
previous conversations here I am thinking of someth
>
>
> Since you are on RHEL 6 I would use ext4 throughout.
>
Great, I'll look into it. However my research suggested a journalled
filesystem is unnecessary for xlogs and I assume ext4 is journalled?
> You say you have I/O problems when "stats jobs" run. Can you describe
> those jobs
> and what t
Ben Carbery wrote:
> I have a postgres server I need to move onto a new OS (RHEL6) on a new VM and
> am looking for advice on
> how to partition the disks to gain some performance improvement.
>
> In the current environment I am given a single VHDD which I have not
> partitioned at all. The SAN
