## Cameron Smith (csm...@stereodllc.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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
