Hi Adrian,
Thanks for the test, I installed also version 17.2 and test with a fresh
newly created db.
At the beginning I cannot reproduce the problem as well.
Than I start adding the extension we use, one after one, and testing in
between.

I found out that the problem appear immediately as soon as I add the
extension pg_stat_statements:

create extension pg_stat_statements WITH SCHEMA public;

alter system set shared_preload_libraries = 'pg_stat_statements';

Can you maybe test as well with this extension?
the other that I installed before that are: pgcrypto and  pg_prewarm.

here the current installed one:

dbtest=# \dx
                                            List of installed extensions
        Name        | Version |   Schema   |
 Description
--------------------+---------+------------+------------------------------------------------------------------------
 pg_prewarm         | 1.2     | public     | prewarm relation data
 pg_stat_statements | 1.11    | public     | track planning and execution
statistics of all SQL statements executed
 pgcrypto           | 1.3     | public     | cryptographic functions
 plpgsql            | 1.0     | pg_catalog | PL/pgSQL procedural language
(4 rows)

dbtest=# select version();
                                                     version

------------------------------------------------------------------------------------------------------------------
 PostgreSQL 17.2 reda build on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
13.3.0-6ubuntu2~24.04) 13.3.0, 64-bit
(1 row)


I'll do some additional tests.

BR
Renzo



On Thu, Dec 19, 2024 at 6:21 PM Adrian Klaver <adrian.kla...@aklaver.com>
wrote:

> On 12/19/24 08:50, Adrian Klaver wrote:
> > On 12/19/24 08:46, Renzo Dani wrote:
> >
> > Again.
> >
> > Reply to list also using Reply All.
> > Ccing list.
> >
> >> Hi Adrian,
> >> here a new version of the script that I just tested produce the same
> >> problem.
> >> The script do not rely now on any additional relation than the ones
> >> defined into the script.
>
> I could not replicate using Ubuntu 22.04 and Postgres 16.6.
>
>  From your original post:
>
> "I reproduced the problem on PostgreSQL versions 16.1 and 17.1."
>
> The latest bug fixes of each are 16.6 and 17.2. I would upgrade to those
> and then try again.
>
> >>
> >> BR
> >> Renzo
> >>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>

Reply via email to