Re: Space Related Errors in Postgres 10.4 Logical Replication
От | Mark Kirkwood |
---|---|
Тема | Re: Space Related Errors in Postgres 10.4 Logical Replication |
Дата | |
Msg-id | c37a4c62-3c68-1627-da65-d51c640f3640@catalyst.net.nz обсуждение исходный текст |
Ответ на | Re: Space Related Errors in Postgres 10.4 Logical Replication (Pavan Teja <pavan.postgresdba@gmail.com>) |
Список | 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@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 >
В списке pgsql-admin по дате отправления: