Postgres Vacuum failed on space - Mailing list pgsql-admin

From Ian Dauncey
Subject Postgres Vacuum failed on space
Date
Msg-id DBAPR08MB56874BF2E776F033653D04C3C0FF9@DBAPR08MB5687.eurprd08.prod.outlook.com
Whole thread Raw
List pgsql-admin

Hi All

 

I tried to run a vacuum against the pg_largeobject table but unfortunately, I ran out of space on my WAL logs causing the vacuum to abort.

The issue I have now is that it has created copies of the data files (I think it was the temp table (vacuum_1) that gets created when vacuum runs. How do I get rid of these files if there is no reference to them in the pg_class table? Also, if I rerun the vacuum will it delete these files.

 

 

Regards

Ian

 

 



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

pgsql-admin by date:

Previous
From: Ron
Date:
Subject: Re: Join for the parent table will not leverage the index scan
Next
From: J T
Date:
Subject: Found xmin before relfrozenxid and logical replication