Feedback-ID: i76984098:Fastmail
Message-ID: <23e8a33e-19af-4a33-b0fa-a225052c264d@aklaver.com>
Date: Tue, 3 Sep 2024 08:16:43 -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>, pgsql-general@lists.postgresql.org
References: <CACW-z_UwPK8RP68ijs5Frn4+iREOSrN99-KFH6g0v3pFVVF1+w@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CACW-z_UwPK8RP68ijs5Frn4+iREOSrN99-KFH6g0v3pFVVF1+w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/23e8a33e-19af-4a33-b0fa-a225052c264d%40aklaver.com>
Precedence: bulk

On 9/2/24 04:37, Sam Son wrote:
> Hi Team,
> 
> I am working on a project where we have applications run on old versions 
> of postgres, we are using *plpythonu* in all Functions extension,

What versions of Postgres?

> 
> Now we have upgraded postgres to latest which does not support plpythonu 
> anymore, So we are facing an issue while restoring dump which has 
> plpythonu, but latest postgres support only plpython3u.

The best way I found to do this is install plpython3u in the old 
versions and convert your plpythonu functions to use plpython3u. Then 
you can drop plpythonu and do the dump/restore. This will also make you 
deal with the fact that Python2 != Python3 and your functions may need 
Python related changes as well.

> 
> *"pg_restore: error: could not execute query: ERROR:  language 
> "plpythonu" does not exist"*
> 
> How to change plpythonu to plpython3u in the dump file before 
> pg_restore. or Does postgres have any option to handle directly via config.
> 
> Thanks in Advance
> 
> Thanks,
> Samson G

-- 
Adrian Klaver
adrian.klaver@aklaver.com