Re: Fwd: When are largobject records TOASTed into pg_toast_2613?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Boussekey <thomas(dot)boussekey(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Fwd: When are largobject records TOASTed into pg_toast_2613?
Date: 2020-08-21 14:14:47
Message-ID: 1802116.1598019287@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thomas Boussekey <thomas(dot)boussekey(at)gmail(dot)com> writes:
> Le ven. 21 août 2020 à 15:10, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Achilleas Mantzios 2020-08-21 14:17:42 Re: Creating many tables gets logical replication stuck
Previous Message Thomas Boussekey 2020-08-21 13:46:21 Fwd: When are largobject records TOASTed into pg_toast_2613?