From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Cameron Smith <csmith(at)stereodllc(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL with BDR - PANIC: could not create replication identifier checkpoint |
Date: | 2016-05-19 18:56:56 |
Message-ID: | 20160519185656.GA309175@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Cameron Smith wrote:
> t:2016-05-19 01:14:51.668 UTC d= p=144 a=PANIC: could not create replication identifier checkpoint "pg_logical/checkpoints/8-F3923F98.ckpt.tmp": Invalid argument
This line corresponds to the following code in BDR's 9.4.4
src/backend/replication/logical/replication_identifier.c:
/*
* no other backend can perform this at the same time, we're protected by
* CheckpointLock.
*/
tmpfd = OpenTransientFile(tmppath,
O_CREAT | O_EXCL | O_WRONLY | PG_BINARY,
S_IRUSR | S_IWUSR);
if (tmpfd < 0)
ereport(PANIC,
(errcode_for_file_access(),
errmsg("could not create replication identifier checkpoint \"%s\": %m",
tmppath)));
This file does not exist in 9.5, but instead we have
src/backend/replication/logical/origin.c which has identical code.
OpenTransientFile calls BasicOpenFile, which in turn calls open() and
propagates the errno. My manpage doesn't list any possible reasons for
open() to return EINVAL, so I'm at a loss about what is happening here.
Maybe this is a filesystem problem?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-05-19 19:13:35 | Re: PQcancel may hang in the recv call |
Previous Message | Cameron Smith | 2016-05-19 18:30:34 | PostgreSQL with BDR - PANIC: could not create replication identifier checkpoint |