Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: 德哥 <digoal(at)126(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi
Date: 2014-04-16 11:34:38
Message-ID: 20140416113438.GF17874@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2014-04-16 19:31:33 +0800, 德哥 wrote:
> CONFIGURE = '... '--with-wal-blocksize=64' '--with-blocksize=32' ...'

Independent of problems around this that probably should be fixed, I
think it's a pretty bad idea to use such a large wal blocksize. That'll
cause a fair amount of write amplification at commits and such.
It might work out well if you only doing bulk loading, but still..

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2014-04-16 11:38:25 Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi
Previous Message 德哥 2014-04-16 11:31:33 Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi