Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1slUYx-0088uc-Aw for pgsql-general@arkaria.postgresql.org; Tue, 03 Sep 2024 14:31:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1slUYv-00CMST-Jd for pgsql-general@arkaria.postgresql.org; Tue, 03 Sep 2024 14:31:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sl5Nz-00Cpge-7p for pgsql-general@lists.postgresql.org; Mon, 02 Sep 2024 11:38:19 +0000 Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sl5Nt-000HaJ-2R for pgsql-general@lists.postgresql.org; Mon, 02 Sep 2024 11:38:18 +0000 Received: by mail-wr1-x42b.google.com with SMTP id ffacd0b85a97d-374d29ad870so10453f8f.3 for ; Mon, 02 Sep 2024 04:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725277091; x=1725881891; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=0/flBy0RSjTH+y8fm1TCwPWSkMmhhYSFTUzxEMpIyeg=; b=YO1mFknQo5X4zZjIYfZLDeALc3Do+3egbgU0I8FCGVzOcRuhbZWvBx3+z6zTVSxNfI XNG5jHgDjWM2dKg/xp1kZDg1opAQZetM5wvPrvuRhU/PkmETabVS6pJu0QKOOsxT9UmR HFgfBZAM+2mNjxRJOt+F/k2cWBhK5Id6+Kit4ZMbBmkpeEaK5KkJ9hw9uLzlxn2l07uE NL8TLa65jD2+ngc2x/h+nqKBwwIkR4yQVJinvpFBQOznBKLS6Eqmtqltl7GPIg0bUawv PN671xm08EdBQEOPwTfAFFhnz6kRToMBYnMjh80t9CDxFJ5zjpR8nJp5755dJyk1vdWk gVUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725277091; x=1725881891; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=0/flBy0RSjTH+y8fm1TCwPWSkMmhhYSFTUzxEMpIyeg=; b=GL4MqoQn8zL21u1D9YTty/n/1U2hZWzCsP5+RYPP/M9RVdr0wabKpdkNJeByuGqGMY alee0R2MCpLRTD79H3eEu8O6DZnNPLmhbuAR2xFjbQY91dcdNDWwGH3fGLfW12NnfenC VmLbsazVBNgwbyHFFeUjy23Ux++6TlsW4mKp7AxtwenK+gUOCGS4bSKaT5qHObxoV8/O 4wVUelCPVZDNGESTJ0k+pAF5fEL1+7X34vg3f5fEj2Ej/+sdm/0uussc0DSF8W7gSV5g FF1QSc+vYQNqH611rd7mv4YFJYTEOXwXHk1Pn4R29Xj/6JAEB7Prozv+wOCROJWLziBI KVRg== X-Gm-Message-State: AOJu0YxHK+ebfLDQVzBc6wnslTETptAqnNi2lYOgLWkLi29D9jNkZeBa YzVRGVCQroHcqvSBgnUKs4gglxjn9HJi4ip3XkE9UY/Lxb3Rc9Bcoh8nqhiw8UA54Sdo17MZ9KB bG5MxcKV42ODd1gfnN4Pn372F8ujfSZsr7JE= X-Google-Smtp-Source: AGHT+IHIfl6iCrVGouGPWAt+tg6G6G9iZ97QlCWYVxlKr0h4CFkJdtQ9/9yhk0qx9qDjRdxoxROp/qzC8ILzFX2JCq4= X-Received: by 2002:adf:9b86:0:b0:374:bb32:656c with SMTP id ffacd0b85a97d-374bf1ca26fmr4390952f8f.39.1725277090745; Mon, 02 Sep 2024 04:38:10 -0700 (PDT) MIME-Version: 1.0 From: Sam Son Date: Mon, 2 Sep 2024 17:07:58 +0530 Message-ID: Subject: Issue with Restore dump with plpythonu, plpython3u installed on postgres16 To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000221e880621216019" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000221e880621216019 Content-Type: text/plain; charset="UTF-8" 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, 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. *"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 --000000000000221e880621216019 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

I am working on a project where we have ap= plications=C2=A0run on old versions of postgres, we are using=C2=A0plpyt= honu=C2=A0in all Functions extension,=C2=A0

Now we have upgraded= postgres to latest which does not support plpythonu anymore, So we are fac= ing an issue while restoring dump which has plpythonu, but latest postgres = support only plpython3u.=C2=A0

"pg_restore:= error: could not execute query: ERROR: =C2=A0language "plpythonu"= ; does not exist"

How to change plpy= thonu to plpython3u in the dump file before pg_restore. or Does postgres ha= ve any option to handle directly via config.=C2=A0

Thanks in Advance

Thanks,
Samson G
<= /div> --000000000000221e880621216019--