Re: Fwd: When are largobject records TOASTed into pg_toast_2613? - Mailing list pgsql-general

From Tom Lane
Subject Re: Fwd: When are largobject records TOASTed into pg_toast_2613?
Date
Msg-id 1802116.1598019287@sss.pgh.pa.us
Whole thread Raw
In response to Fwd: When are largobject records TOASTed into pg_toast_2613?  (Thomas Boussekey <thomas.boussekey@gmail.com>)
List pgsql-general
Thomas Boussekey <thomas.boussekey@gmail.com> writes:
> Le ven. 21 août 2020 à 15:10, Laurenz Albe <laurenz.albe@cybertec.at> a
> écrit :
>> The safest way would be to upgrade with pg_dumpall/psql.

> The `pg_dumpall` command will also copy the content and the existence of
> the `pg_toast_2613` table, isn't it?

No.  pg_dumpall does not do anything with system catalogs per se.

> Moreover, it will generate a large downtime

Yeah.  It's a tradeoff of safety versus downtime.  If that toast table
is physically empty (I would not bet on it without checking), then you
could manually hack up pg_class to remove the toast table, but there's
a nontrivial risk of permanently hosing your database by messing that
up.

            regards, tom lane



pgsql-general by date:

Previous
From: Thomas Boussekey
Date:
Subject: Fwd: When are largobject records TOASTed into pg_toast_2613?
Next
From: Achilleas Mantzios
Date:
Subject: Re: Creating many tables gets logical replication stuck