Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi
От | Heikki Linnakangas |
---|---|
Тема | Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi |
Дата | |
Msg-id | 534E655A.8030200@vmware.com обсуждение исходный текст |
Ответ на | Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write
to file "pg_xlog/xlogtemp.3590": No space left on devi
Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi |
Список | pgsql-bugs |
On 04/16/2014 01:59 PM, Andres Freund wrote: > On 2014-04-16 13:50:35 +0300, Heikki Linnakangas wrote: >> On 04/16/2014 11:20 AM, digoal@126.com wrote: >>> HI, >>> I can reproduce this. >> >> Ok. Can you try with the attached patch applied, please? > > Perhaps this should also support partial writes, akin to > 79ce29c734c6a652b2f7193bda537cff0c8eb8c1? I don't find it all that > unreasonble for the OS to refuse 16MB - or even bigger - writes in some > scenarios. The write in XLogFileInit is always 8kB (XLOG_BLCKSZ). But yeah, it might make sense to retry. Although I wonder why XLogFileInit would be particularly vulnerable to short writes. I'm afraid if we fix that, next we'll start seeing failures from other writes, to data files. But wait for Digoal to run with the extra let's see if this was in fact a short write. Could also be a quota or similar. - Heikki
В списке pgsql-bugs по дате отправления: