| From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL with BDR - PANIC: could not create replication identifier checkpoint |
| Date: | 2016-05-19 19:19:55 |
| Message-ID: | 20160519191955.GA1477@squirrel.exwg.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
## Cameron Smith (csmith(at)stereodllc(dot)com):
> 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
> t:2016-05-19 01:14:51.671 UTC d= p=9729 a=WARNING: could not create relation-cache initialization file "global/pg_internal.init.9729": Invalid argument
This and the other "Invalid Argument" errors give the impression that
your "power issue" has wrecked your filesystem - as Alvaro already
pointed out, there's no sane way that an open() returns EINVAL in
PostgreSQL on any "recommended" filesystem.
This shouldn't happen with any decently modern filesystem and "safe"
hardware. Did you tweak anything on your filesystem? Did you check
your storage stack against https://wiki.postgresql.org/wiki/Reliable_Writes?
Regards,
Christoph
--
Spare Space
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-19 19:32:08 | Re: PQcancel may hang in the recv call |
| Previous Message | Cameron Smith | 2016-05-19 19:15:49 | Re: PostgreSQL with BDR - PANIC: could not create replication identifier checkpoint |