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

HI,

Use this snapshot the problem fixed, thanks Heikki and Andres's help.

Use correctly-sized buffer when zero-filling a WAL file.
| author | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> | |
| | Wed, 16 Apr 2014 07:21:09 +0000 (10:21 +0300) |
| committer | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> | |
| | Wed, 16 Apr 2014 07:26:36 +0000 (10:26 +0300) |
| commit | 848b9f05ab283724dd063d936a92568c1fdf422b |
| tree | e6f0804cb145b3c09841bc91a9dd6e07e5778551 | tree | snapshot |
| parent | ab76d8e9d672c661fe8ce4d9405dc8956b8ece9d | commit | diff |
Use correctly-sized buffer when zero-filling a WAL file.

I mixed up BLCKSZ and XLOG_BLCKSZ when I changed the way the buffer is
allocated a couple of weeks ago. With the default settings, they are both
8k, but they can be changed at compile-time.

| src/backend/access/transam/xlog.c | | diff | blob | blame | history |

--
公益是一辈子的事,I'm Digoal,Just Do It.

在 2014-04-16 07:28:52，"Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com> 写道：
>On 04/16/2014 02:17 PM, 德哥 wrote:
>> LOG: write() in XLogFileInit returned 40960: Success
>
>Oh, that's interesting. Have you tweaked BLCKSZ or XLOG_BLCKSZ? If you
>have, try with a fresh checkout - I just fixed a bug in that code where
>I had used BLCKSZ instead of XLOG_BLCKSZ in the allocation of the
>buffer. They're the same by default, but if you've changed them, that
>might be it.
>
>- Heikki