Re: Space Related Errors in Postgres 10.4 Logical Replication

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Space Related Errors in Postgres 10.4 Logical Replication
Date: 2018-08-27 22:18:11
Message-ID: c37a4c62-3c68-1627-da65-d51c640f3640@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)debian(dot)org
> <mailto:myon(at)debian(dot)org>> wrote:
>
> Re: pavan95 2018-08-20 <1534743876524-0(dot)post(at)n3(dot)nabble(dot)com
> <mailto:1534743876524-0(dot)post(at)n3(dot)nabble(dot)com>>
> > *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 *
>
> This is simply what it says: your disk was full. You need to make sure
> PG has enough free disk space available.
>
> Christoph
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2018-08-28 03:31:39 Re: Database Connectivity Issue with DB Lookup
Previous Message Tim Cross 2018-08-27 22:05:18 Re: FW: Setting up SSL for postgre