Re: Redo the filenode link in tablespace

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: tel medola <tel(dot)medola(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Redo the filenode link in tablespace
Date: 2017-06-08 13:33:09
Message-ID: f2980847-1f2a-c4e5-66d6-2dab084acb9d@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/07/2017 06:05 PM, tel medola wrote:
> Holy shit! (sorry)....
>
> Thanks, thanks!!!
>
> It worked!
>
> My goodness!!!!
> After I point to the filnode, I did a reindex on the toast and some
> records have already been located.

Great, glad that it worked. Just realize we have been modifying a system
catalog(pg_class) directly, which is generally a dangerous thing to do.
I would take a backup of the table and data via pg_dump to be on the
safe side. This assumes you have the space to store it, though the
backup when compressed should be a good deal smaller then the actual
table size. You might also think about moving the tables to a new
tablespace to get a clean tablespace directory. Again this assumes space
available.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message ADSJ (Adam Sjøgren) 2017-06-08 15:13:24 Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
Previous Message Neil Anderson 2017-06-08 11:59:31 Re: pg_catalog tables don't have constraints?