pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Pg_upgrade error could not load library from 7.14/8.4 to 10.10 version
Date: Thu, 19 Sep 2019 17:07:22 +0300
Message-ID: <1cbc7491-b9a3-8130-b959-2f3a2e4dd4a2@matrix.gatewaynet.com> (raw)
In-Reply-To: <22046.1568901429@sss.pgh.pa.us>
References: <e95cf94c-b7f1-1963-6647-6335785870d9@zunibal.com>
	<4519fdad-d747-cd39-f6a2-33e7db1f3324@matrix.gatewaynet.com>
	<a82dd9e3-d388-24d1-95bb-cdb1ac7ee758@zunibal.com>
	<22046.1568901429@sss.pgh.pa.us>

On 19/9/19 4:57 μ.μ., Tom Lane wrote:
> Ekaterina Amez <ekaterina.amez@zunibal.com> writes:
>> El 19/9/19 a las 10:07, Achilleas Mantzios escribió:
>>> On 19/9/19 10:49 π.μ., Ekaterina Amez wrote:
>>>> 2019-09-19 08:53:50.345 CEST [2283] postgres@template1 ERROR:  could not load library "/usr/lib/postgresql/8.4/lib/plpgsql.so": /usr/lib/postgresql/8.4/lib/plpgsql.so: undefined symbol: SPI_push
> This error is clearly due to trying to load the 8.4 version of plpgsql.so
> into the v10 server.

Yup, in the log, right after the "undefined symbol: SPI_push" ERROR there are entries about logical replication, those could not have come from the 8.4 server. Arghhh I didn't watch close enough. Thanx

>
>> With these results, finally I've:
>>       1- modified template1 in PG 8.4 server to include plpgsql language,
>> so it can be inherited in new databases created from this template.
>>       2- Dropped and recreated my database (let's call it newdb).
> This probably fixed it by ensuring that the plpgsql support functions
> were declared with the standard value of probin.
>
>> The conclusion is that I can avoid the use of plpgsql.so library. My
>> question now would be related about the creation of the language in
>> version 8.4: is it better to create it at template level or at database
>> level?
> I would not sweat too much about this, since you don't intend to keep
> using 8.4 (or at least I hope not).  Since 9.0, plpgsql is automatically
> installed at initdb time and there's no need for an additional copy.
>
> 			regards, tom lane
>
>


-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt






view thread (13+ messages)  latest in thread

Message-ID: <1cbc7491-b9a3-8130-b959-2f3a2e4dd4a2@matrix.gatewaynet.com>
Permalink:  ../1cbc7491-b9a3-8130-b959-2f3a2e4dd4a2@matrix.gatewaynet.com/
Also on:    postgresql.org/message-id/1cbc7491-b9a3-8130-b959-2f3a2e4dd4a2@matrix.gatewaynet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Pg_upgrade error could not load library from 7.14/8.4 to 10.10 version
  In-Reply-To: <1cbc7491-b9a3-8130-b959-2f3a2e4dd4a2@matrix.gatewaynet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox