Bug 31333 - PostgreSQL 15 tablefunc has undefined symbol: pg_global_prng_state
Summary: PostgreSQL 15 tablefunc has undefined symbol: pg_global_prng_state
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-27 18:31 CET by Pierre Fortin
Modified: 2023-01-09 09:18 CET (History)
0 users

See Also:
Source RPM: postgresql15-15.1-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Pierre Fortin 2022-12-27 18:31:05 CET
Description of problem:  Just upgraded PostgreSQL from 14 to 15.  The "tablefunc" extension was missing in 14; it's available in 15, but fails with:

An error occurred when executing the SQL command:
CREATE EXTENSION tablefunc

ERROR: could not load library "/usr/lib64/postgresql/tablefunc.so": /usr/lib64/postgresql/tablefunc.so: undefined symbol: pg_global_prng_state


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


How reproducible:


Steps to Reproduce:
1. 
2.
3.
Comment 1 Lewis Smith 2022-12-27 20:47:13 CET
Thanks for the report.
Assuming the error "undefined symbol: pg_global_prng_state" is in postgresql15-contrib.

 $ urpmf /usr/lib64/postgresql/tablefunc.so
postgresql13-contrib:/usr/lib64/postgresql/tablefunc.so
postgresql15-contrib:/usr/lib64/postgresql/tablefunc.so
Yes, it did disappear from 14.

Assigning to NicolasS, official maintainer of postgresql15.

Assignee: bugsquad => nicolas.salguero
Summary: PostgreSQL tablefunc has undefined symbol: pg_global_prng_state => PostgreSQL 15 tablefunc has undefined symbol: pg_global_prng_state
Source RPM: (none) => postgresql15-15.1-1.mga9.src.rpm

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

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

Comment 2 Nicolas Salguero 2023-01-09 09:18:21 CET
Hi,

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

Best regards,

Nico.

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


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