Bug 31341 - plpgsql.so: undefined symbol: SPI_execute_extended
Summary: plpgsql.so: undefined symbol: SPI_execute_extended
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Salguero
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-30 12:24 CET by Pierre Fortin
Modified: 2023-01-09 09:18 CET (History)
0 users

See Also:
Source RPM: postgresql15-plpgsql
CVE:
Status comment:


Attachments

Description Pierre Fortin 2022-12-30 12:24:30 CET
Description of problem:  undefined symbol in plpgsql.so


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. use psql
2. try to use plpgsql as follows...

test=# do $$
test$# select * from file limit 2;
test$# end; $$;
ERROR:  could not load library "/usr/lib64/postgresql/plpgsql.so": /usr/lib64/postgresql/plpgsql.so: undefined symbol: SPI_execute_extended

where "file" is a table in database "test".

"select * from file limit 2;" doesn't need to be inside a plpgsql block; but it's the simplest example to illustrate the issue.
Comment 1 Lewis Smith 2022-12-30 20:07:10 CET
Thank you for the report.
Please say which version of Postgresql you are using: 13 or 15.

Source RPM: (none) => postgresql15-plpgsql, postgresql13-plpgsql
CC: (none) => lewyssmith

Comment 2 Pierre Fortin 2022-12-30 22:02:37 CET
Sorry.  15...  it was part of the recent update -- I update Cauldron daily if there's anything; though kernel/glibc reboots are scheduled.
Comment 3 Lewis Smith 2023-01-02 19:57:34 CET
Thanks.
Assigning accordingly to NicolasS for postgresql15.

Assignee: bugsquad => nicolas.salguero
CC: lewyssmith => (none)
Source RPM: postgresql15-plpgsql, postgresql13-plpgsql => postgresql15-plpgsql

Nicolas Salguero 2023-01-05 10:45:22 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=31354

Comment 4 Nicolas Salguero 2023-01-09 09:18:19 CET
Hi,

As that bug has the same cause as bug 31354, I close it.

Best regards,

Nico.

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.