From: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Space Related Errors in Postgres 10.4 Logical Replication |
Date: | 2018-08-20 05:44:36 |
Message-ID: | 1534743876524-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi all,
I have configured Postgres Native Logical Replication for 2 servers(a
publisher and subscriber). I have came across a new error in the postgres
log file as shown as below:
*PUBLISHER LOG:*
*2018-08-20 10:34:55.801 IST [24955] user(at)db ERROR: could not create
directory "pg_replslot/mysub_14211111_sync_111111.tmp": No space left on
device *
*2018-08-20 10:34:56.036 IST [34222] user(at)db ERROR: could not create file
"pg_replslot/mysub/state.tmp": No space left on device*
*2018-08-20 10:34:56.053 IST [23444] user(at)db WARNING: could not create
relation-cache initialization file "global/pg_internal.init.11331": No space
left on device*
*2018-08-20 10:34:56.053 IST [23444] user(at)db DETAIL: Continuing anyway, but
there's something wrong.*
My questions are:
1) why has the error occurred?
2) What is the immediate to do task to reduce this error?
3) How to prevent it's forthcoming occurrence (or) How to make changes to
reduce this error?
This is my first Logical Replication setup. Kindly help me with these
issues..
Thanks in Advance.
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2018-08-20 06:17:02 | Re: Logical replication monitoring |
Previous Message | Maycon Oleczinski | 2018-08-16 19:56:01 | Re: pgAdmin 4 v3.1 & v3.2 eternal loading |