pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSpace Related Errors in Postgres 10.4 Logical Replication
5+ messages / 4 participants
[nested] [flat]
* Space Related Errors in Postgres 10.4 Logical Replication
@ 2018-08-20 05:44 pavan95 <pavan.postgresdba@gmail.com>
0 siblings, 2 replies; 5+ messages in thread
From: pavan95 @ 2018-08-20 05:44 UTC (permalink / raw)
To: 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@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@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@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@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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Space Related Errors in Postgres 10.4 Logical Replication
@ 2018-08-20 06:50 pavan95 <pavan.postgresdba@gmail.com>
parent: pavan95 <pavan.postgresdba@gmail.com>
1 sibling, 0 replies; 5+ messages in thread
From: pavan95 @ 2018-08-20 06:50 UTC (permalink / raw)
To: pgsql-admin
Hi all,
Looking forward to hear from you regarding the above errors.
Thanks in advance.
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Space Related Errors in Postgres 10.4 Logical Replication
@ 2018-08-27 18:38 Christoph Berg <myon@debian.org>
parent: pavan95 <pavan.postgresdba@gmail.com>
1 sibling, 1 reply; 5+ messages in thread
From: Christoph Berg @ 2018-08-27 18:38 UTC (permalink / raw)
To: pavan95 <pavan.postgresdba@gmail.com>; +Cc: pgsql-admin
Re: pavan95 2018-08-20 <1534743876524-0.post@n3.nabble.com>
> *PUBLISHER LOG:*
> *2018-08-20 10:34:55.801 IST [24955] user@db ERROR: could not create
> directory "pg_replslot/mysub_14211111_sync_111111.tmp": No space left on
> device *
This is simply what it says: your disk was full. You need to make sure
PG has enough free disk space available.
Christoph
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Space Related Errors in Postgres 10.4 Logical Replication
@ 2018-08-27 18:58 Pavan Teja <pavan.postgresdba@gmail.com>
parent: Christoph Berg <myon@debian.org>
0 siblings, 1 reply; 5+ messages in thread
From: Pavan Teja @ 2018-08-27 18:58 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-admin
But enough space was available. Don't know why it occurred.
Regards,
Pavan
On Tue, Aug 28, 2018, 12:08 AM Christoph Berg <myon@debian.org> wrote:
> Re: pavan95 2018-08-20 <1534743876524-0.post@n3.nabble.com>
> > *PUBLISHER LOG:*
> > *2018-08-20 10:34:55.801 IST [24955] user@db ERROR: could not create
> > directory "pg_replslot/mysub_14211111_sync_111111.tmp": No space left on
> > device *
>
> This is simply what it says: your disk was full. You need to make sure
> PG has enough free disk space available.
>
> Christoph
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Space Related Errors in Postgres 10.4 Logical Replication
@ 2018-08-27 22:18 Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
parent: Pavan Teja <pavan.postgresdba@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Mark Kirkwood @ 2018-08-27 22:18 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Maybe check if you have any quotas set up that might be limiting the
space available. Alternatively it might just be that the space required
is bigger than you think (i.e usage grows so fast that casual monitoring
does not pick it up).
regards
Mark
On 28/08/18 06:58, Pavan Teja wrote:
> But enough space was available. Don't know why it occurred.
>
> Regards,
> Pavan
>
> On Tue, Aug 28, 2018, 12:08 AM Christoph Berg <myon@debian.org
> <mailto:myon@debian.org>> wrote:
>
> Re: pavan95 2018-08-20 <1534743876524-0.post@n3.nabble.com
> <mailto:1534743876524-0.post@n3.nabble.com>>
> > *PUBLISHER LOG:*
> > *2018-08-20 10:34:55.801 IST [24955] user@db ERROR: could not create
> > directory "pg_replslot/mysub_14211111_sync_111111.tmp": No space
> left on
> > device *
>
> This is simply what it says: your disk was full. You need to make sure
> PG has enough free disk space available.
>
> Christoph
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2018-08-27 22:18 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-08-20 05:44 Space Related Errors in Postgres 10.4 Logical Replication pavan95 <pavan.postgresdba@gmail.com>
2018-08-20 06:50 ` pavan95 <pavan.postgresdba@gmail.com>
2018-08-27 18:38 ` Christoph Berg <myon@debian.org>
2018-08-27 18:58 ` Pavan Teja <pavan.postgresdba@gmail.com>
2018-08-27 22:18 ` Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox