Re: plpgsql_check_function issue after upgrade

2022-12-04 Thread shashidhar Reddy
Pavel, Below is the back trace result libffi6-dbg libgcc1-dbg libkrb5-dbg libstdc++6-8-dbg libxml2-dbg postgresql-13-dbgsym postgresql-13-pldeb ugger-dbgsym zlib1g-dbg On Mon, Dec 5, 2022 at 11:28 AM Pavel Stehule wrote: > Hi > > > po 5. 12. 2022 v 6:49 odesílatel shashidhar Reddy < > shashidh

Re: Libpq linked to LibreSSL

2022-12-04 Thread Marco Bambini
I am using Ubuntu 14.04.5 LTS (64b bit). If I don't modify anything then my test application runs fine and it load OpenSSL 1.0.1f 6 Jan 2014 from the default directory. ldd libpq.so linux-vdso.so.1 => (0x7fff74af1000) libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0

Re: plpgsql_check_function issue after upgrade

2022-12-04 Thread Pavel Stehule
Hi po 5. 12. 2022 v 6:49 odesílatel shashidhar Reddy < shashidharreddy...@gmail.com> napsal: > Pavel, > > Where can I get list-dbgsym-packages.sh script? > https://manpages.debian.org/testing/debian-goodies/find-dbgsym-packages.1.en.html https://wiki.ubuntu.com/DebuggingProgramCrash please, d

Re: plpgsql_check_function issue after upgrade

2022-12-04 Thread shashidhar Reddy
Pavel, Where can I get list-dbgsym-packages.sh script? On Wed, Nov 30, 2022 at 10:04 AM Pavel Stehule wrote: > > > st 30. 11. 2022 v 5:28 odesílatel Pavel Stehule > napsal: > >> >> >> st 30. 11. 2022 v 1:38 odesílatel shashidhar Reddy < >> shashidharreddy...@gmail.com> napsal: >> >>> I have tr

Re: Libpq linked to LibreSSL

2022-12-04 Thread Michael Paquier
On Sun, Dec 04, 2022 at 09:02:07AM +0100, Marco Bambini wrote: > After several attempts (and runtime crashes), I am asking for help > with how to compile libpq with LibreSSL support (both dynamic and > static links would be OK to me). > I know how to compile libpq with OpenSSL support, but I need t

Re: Q: error on updating collation version information

2022-12-04 Thread Karsten Hilbert
Is this to be expected ? PG 15.1 on Debian: gnumed_v22=# select *, pg_collation_actual_version(oid), pg_encoding_to_char(collencoding) from pg_collation where collname = 'zh_TW'; -[ RECORD 1 ]---+ oid | 12985 collnam

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

2022-12-04 Thread Karsten Hilbert
Am Sun, Dec 04, 2022 at 06:05:30PM +0100 schrieb Alban Hertroys: > > I mean, pg_get_functiondef output being a server runtime artifact it might > > well change between server versions, no ? > > I meant to write: “I would also generate new diffs right > _before and_ after…”, precisely for that reas

Re: Q: error on updating collation version information

2022-12-04 Thread Karsten Hilbert
Am Sun, Dec 04, 2022 at 10:09:47AM -0800 schrieb Adrian Klaver: > >>following an ICU upgrade, collations in a stock Debian PG 15.1 > >>cluster now have divergent version information in pg_collations. > > > >Correction: this is following a libc upgrade 2.35 -> 2.36 > > So to be clear this database

Re: delete statement returning too many results

2022-12-04 Thread Arlo Louis O'Keeffe
> On 29. Nov 2022, at 18:35, Tom Lane wrote: > > Harmen writes: >> On Mon, Nov 28, 2022 at 12:11:53PM -0500, Tom Lane wrote: >>> So basically it's unsafe to run the sub-select more than once, >>> but the query as written leaves it up to the planner whether >>> to do that. I'd suggest rephrasi

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

2022-12-04 Thread Ron
On 12/4/22 11:05, Alban Hertroys wrote: On 3 Dec 2022, at 20:55, Karsten Hilbert wrote: You would need to wrap the function creation calls into some automation to generate and store those diffs, comparing it back, etc, but that may be doable. I would also generate new diffs right after major

Re: Q: error on updating collation version information

2022-12-04 Thread Adrian Klaver
On 12/4/22 04:35, Karsten Hilbert wrote: Am Sun, Dec 04, 2022 at 01:22:02PM +0100 schrieb Karsten Hilbert: following an ICU upgrade, collations in a stock Debian PG 15.1 cluster now have divergent version information in pg_collations. Correction: this is following a libc upgrade 2.35 -> 2.36

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

2022-12-04 Thread Alban Hertroys
> On 3 Dec 2022, at 20:55, Karsten Hilbert wrote: > >> You would need to wrap the function creation calls into some automation to >> generate and store those diffs, comparing it back, etc, but that may be >> doable. I would also generate new diffs right after major version updates of >> the

Re: Q: error on updating collation version information

2022-12-04 Thread Karsten Hilbert
Am Sun, Dec 04, 2022 at 01:22:02PM +0100 schrieb Karsten Hilbert: > following an ICU upgrade, collations in a stock Debian PG 15.1 > cluster now have divergent version information in pg_collations. Correction: this is following a libc upgrade 2.35 -> 2.36 Karsten -- GPG 40BE 5B0E C98E 1713 AFA6

Re: Q: error on updating collation version information

2022-12-04 Thread Karsten Hilbert
Am Sun, Dec 04, 2022 at 01:22:02PM +0100 schrieb Karsten Hilbert: > gnumed_v22=> ALTER COLLATION pg_catalog."br_FR@euro" REFRESH VERSION; > ERROR: collation "pg_catalog.br_FR@euro" for encoding "UTF8" does not > exist The OS (libc) does seem to know that collation: @hermes:

Q: error on updating collation version information

2022-12-04 Thread Karsten Hilbert
Dear all, following an ICU upgrade, collations in a stock Debian PG 15.1 cluster now have divergent version information in pg_collations. Now gnumed_v22=> ALTER COLLATION pg_catalog."br_FR@euro" REFRESH VERSION; ERROR: collation "pg_catalog.br_FR@euro" for encoding "UTF8" does n

Libpq linked to LibreSSL

2022-12-04 Thread Marco Bambini
Hi all, After several attempts (and runtime crashes), I am asking for help with how to compile libpq with LibreSSL support (both dynamic and static links would be OK to me). I know how to compile libpq with OpenSSL support, but I need to force it to link to LibreSSL. Any help would be really a