On Monday 07 October 2013 15:23:33 Marcin Mańk wrote:
> On Thu, Oct 3, 2013 at 11:56 PM, Michal TOMA wrote:
> > Now I have:
> > checkpoint_completion_target = 0.9
> > wal_buffers = 8MB
> > checkpoint_segments = 16
> > checkpoint_timeout = 20min
> > shared_bu
On Monday 07 October 2013 21:33:14 Jeff Janes wrote:
> On Mon, Oct 7, 2013 at 11:44 AM, Michal TOMA wrote:
> > I gave it in my first post. It is a software raid 1 of average 7200 rpm
> > disks
> > (Hitachi HDS723020BLE640) for the main tablespace and a software raid 1
> > of SSDs for onother table
On Mon, Oct 7, 2013 at 11:44 AM, Michal TOMA wrote:
> I gave it in my first post. It is a software raid 1 of average 7200 rpm
> disks
> (Hitachi HDS723020BLE640) for the main tablespace and a software raid 1 of
> SSDs for onother tablespace and alos the partition holding the pg_xlog
> directory.
I gave it in my first post. It is a software raid 1 of average 7200 rpm disks
(Hitachi HDS723020BLE640) for the main tablespace and a software raid 1 of
SSDs for onother tablespace and alos the partition holding the pg_xlog
directory.
The problem is not the workload as the application is a web c
On Mon, Oct 7, 2013 at 6:23 AM, Marcin Mańk wrote:
> On Thu, Oct 3, 2013 at 11:56 PM, Michal TOMA wrote:
>
>>
>> This is what I can see in the log:
>> 2013-10-03 13:58:56 CEST LOG: checkpoint starting: xlog
>> 2013-10-03 13:59:56 CEST LOG: checkpoint complete: wrote 448 buffers
>> (0.2%);
The database is about 1TB large.
Thera are mainly 4 tables 2 with row sizes about 1000 bytes and 2 with rows
with about 200 bytes but contaniong also several usually large (the size of
an average webpage) text fields.
My initial setting was 16GB of shared buffers I tried with 2GB and did not
not
On Thu, Oct 3, 2013 at 11:56 PM, Michal TOMA wrote:
>
> Now I have:
> checkpoint_completion_target = 0.9
> wal_buffers = 8MB
> checkpoint_segments = 16
> checkpoint_timeout = 20min
> shared_buffers = 2GB
> log_checkpoints = on
>
> This is what I can
Hello Alban,
Yes I think I'm saturating the HDD IO but the problem is that the only thing
that runs on that server is postgres itself.
I have two tablespeces one on a SSD software raid 1 another one on a HDD
software raid 1.
The disk which is saturating is the HDD and the pg_xlog directory is on
On Oct 3, 2013, at 23:56, Michal TOMA wrote:
> I have a problem on my pg 9.2.4 setup (OpenSuse 12.2, kernel 3.2.13).
> My pg_xlog directory is growing uncontrolably untill it fills the partition.
> The database is under heavy write load and is spread on two tablesapces one
> on a ssd software r
I have it set to 0 already.
On Friday 04 October 2013 00:16:28 Ken Brush wrote:
> Try setting the following in your postgresql.conf:
>
> wal_keep_segments = 0
>
> On Thu, Oct 3, 2013 at 2:56 PM, Michal TOMA wrote:
> > Hello,
> >
> > I have a problem on my pg 9.2.4 setup (OpenSuse 12.2, kernel 3.2
Try setting the following in your postgresql.conf:
wal_keep_segments = 0
On Thu, Oct 3, 2013 at 2:56 PM, Michal TOMA wrote:
> Hello,
>
> I have a problem on my pg 9.2.4 setup (OpenSuse 12.2, kernel 3.2.13).
> My pg_xlog directory is growing uncontrolably untill it fills the
> partition. The da
11 matches
Mail list logo
