Re: vacuumlo

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Ian Dauncey <Ian(dot)Dauncey(at)bankzero(dot)co(dot)za>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: vacuumlo
Date: 2021-08-17 12:17:47
Message-ID: CAOBaU_YNAsTVHXS1UFw_XBt2YOZjwsJ3KMnZXrwqKb+86WAhpg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

Hi,

On Tue, Aug 17, 2021 at 7:52 PM Ian Dauncey <Ian(dot)Dauncey(at)bankzero(dot)co(dot)za> wrote:
>
> I need to run the vacuumlo command against our production database.
>
> Being a PostgresQL database utility, it should be 100% safe to run and should not delete/drop active data.

It's safe as long as you're aware of what this tool is doing. As
mentioned in https://www.postgresql.org/docs/current/vacuumlo.html:

> vacuumlo is a simple utility program that will remove any “orphaned” large objects from a PostgreSQL database. An orphaned large object (LO) is considered to be any LO whose OID does not appear in any oid or lo data column of the database.

So:

> I have run it in our QA environment with success, but now they are having a few application issues and I have told them that the issues cannot be related to the vacuumlo utility as it is a PostgresQL utility.

The most likely explanation is that your database somehow has large
object that are not referenced in an "oid" or "lo" column. If that's
the case, vacuumlo will delete some of your data, as you didn't you
your part of the contract required to use that tool, which is to
properly reference large objects reference.

In response to

  • vacuumlo at 2021-08-17 11:51:47 from Ian Dauncey

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2021-08-17 20:15:02 Re: Join for the parent table will not leverage the index scan
Previous Message Ian Dauncey 2021-08-17 11:51:47 vacuumlo

Browse pgsql-general by date

  From Date Subject
Next Message Andy Hall 2021-08-17 12:21:51 Re: postgres disconnects on master after setting up replication
Previous Message Dave Cramer 2021-08-17 12:09:30 Re: postgres disconnects on master after setting up replication