Feedback-ID: i76984098:Fastmail
Message-ID: <c35bd12e-a362-4089-9e80-a0696b3e9844@aklaver.com>
Date: Wed, 4 Sep 2024 08:04:45 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Issue with Restore dump with plpythonu, plpython3u installed on
 postgres16
To: Sam Son <sam89.g@gmail.com>
Cc: Muhammad Usman Khan <usman.k@bitnine.net>,
 pgsql-general@lists.postgresql.org
References: <CACW-z_UwPK8RP68ijs5Frn4+iREOSrN99-KFH6g0v3pFVVF1+w@mail.gmail.com>
 <CAPnRvGu-7B7J1i624KcJ-V2nUkuqGLsDT4Ae=EGbAPXJ=8A4fQ@mail.gmail.com>
 <f53c8d83-bf1b-4c04-a2ed-3ae5116aa582@aklaver.com>
 <a1ead53f-8348-4dbd-b9f1-6e9c4f2633f0@aklaver.com>
 <CACW-z_Xunr6cKL89h-uOE1sfvJ0E0thL+5k6NwT+B-PNq_=_=g@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CACW-z_Xunr6cKL89h-uOE1sfvJ0E0thL+5k6NwT+B-PNq_=_=g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/c35bd12e-a362-4089-9e80-a0696b3e9844%40aklaver.com>
Precedence: bulk

On 9/4/24 03:48, Sam Son wrote:
> Hi Adrian, Muhammad,
> 
> Thanks for the quick response.
> 
> For new I cannot do changes in old version DB, since it is deployed 
> remotely and i dont have any access. And it has to be done from multiple 
> servers.
> 
> As a work around I tried two solutions.

Both of which depend on the plpythonu functions running with plpython3u, 
in other words that they are Python3 compatible. Have you verified that?

> 
> *Solution 1:*
> 
> After downloading and extracting the dump, convert the pgdump file to 
> sql file which is editable.
> 
> *    pg_restore -f out_dump.sql dump.pgdump*
> 
> Replace all the plpythonu references with plputhon3u.
> 
> Restore using the sql file.
> 
> *    sudo -H -u postgres psql -p 5433 -d db_name <  out_dump.sql*

I would suggest working on the schema portion separate from the data:

pg_restore -s -f out_dump_schema.sql dump.pgdump*

Do your search and replace, restore to database and then:

pg_restore -a ...  dump.pgdump*

Where -a is data only.

In fact if you have control of the pg_dump break it into two parts:

pg_dump -s ...  --schema

pg_dump -a ...  --data only

> 
> 
> *Solution 2:*
> 
> After downloading and extracting the dump, get the list of items in dump 
> (Schemas, tables, table data, Index, functions, etc).
> 
> *    pg_restore -l dump.pgdump > dump.txt*
> 
> Delete all the function references which have plpython3u.

I'm guessing you meant plpythonu above.


> *Question:*
> 
> Our database size is 500GB,
> 
> Do we see any performance impact using solution 1. Since solution 1 is 
> using sql file load and solution 2 is using pg_restore directly.
> 
> Kindly recommend what to choose, solution 1 or solution 2 or any other 
> workaround to restore.

Personally I would go with solution 1 with the modifications I suggested.

> 
> 
> Thanks,
> Samson G
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com