Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tONLl-005uvv-6L for pgsql-general@arkaria.postgresql.org; Thu, 19 Dec 2024 20:42:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tONLj-00H9SC-SR for pgsql-general@arkaria.postgresql.org; Thu, 19 Dec 2024 20:42:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tONLj-00H9S4-ED for pgsql-general@lists.postgresql.org; Thu, 19 Dec 2024 20:42:23 +0000 Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tONLb-000dl0-Qe for pgsql-general@postgresql.org; Thu, 19 Dec 2024 20:42:22 +0000 Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5d7e3f1fdafso2338314a12.0 for ; Thu, 19 Dec 2024 12:42:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734640934; x=1735245734; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BU8rq1H3yJe5WxtLCHHSx72X9zpHRHbvPFupADZZO70=; b=Le5mHSlwEpKg8uZDIUWwolqte40ClcHDrZNKFYEuo2tKoDvHCKXdSYe6+slLxC/1sJ cJtOkKXLdgy+R9bw5jiP4TZNKLXHwrCiGtG0vur+Z+Nu1N2NBWQ8se1MzgkNtb+0o0L1 17WoY6TuhgJlAQMo0Y3wu67gA5XljdfjGuiyJaZkQJJ/MJ6BU6OGuPxp9Iusy60Hu99b DWWonudHz+V2B8UxeanNjv9OWT0vyEePG8J9lChOgrGXWXr3mHOUYQ9YABsuBrwZNItg AdGCsdmE9lm7FFvKxhvGwFHY1Kh+s2NKuZEeMWbvf80FIjVQ3jYnYsAF29N4VI/hH0rd HGUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734640934; x=1735245734; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BU8rq1H3yJe5WxtLCHHSx72X9zpHRHbvPFupADZZO70=; b=fRCTOTm5WKJscaSvHwJ7xId4//pEH+vbuzQN9L+cHwXEGMcraCS+T/qWudHhx/cyao IvMytX8SN6J38RZUFUCU56/0Fp/zphRXYKK5/xeS5rkRX2LXd4dmY2yyxSKAqUyxc5xu /o9anZxuDBNul8OceYdGPRh1OhXx6hgbKXG/FZCD3erjfR3WsVULenlrWIvkxIhCOcHA U86v6vcZFlb48RWl9GOE/VTCIh56AZ8oegOKvdlJ9fo0cEEz0YhJ+WIRaHr+KBaqOjAc 60EGwpu0BQ6JuOVPK6M6uWvIngdq8uQXC8LgJIrzK4Y0WYnIdEbZ5nq/uV0t73+vrrcw A4gA== X-Gm-Message-State: AOJu0Ywc+x3LrsicrAOoZsTNJggaUV/X/AdTGdEpBlqsCfk0hvhhAgkx gKNYavmn0gfg78ozOC+iOXyCFMqiF3AaDNpxA8J+3m2xFU61J/hdqO6J5f0CMb3j5/8v40JY+Dp 4byS1wOuWFOiH2V48OXE+Il2oaBn+deg0 X-Gm-Gg: ASbGncveD9Cxp5XeT1OGIvGapH0t53xWzV7cdd/kAMPKQf4KP6ckkFcX4qnOD9vcHZJ tk8suwYpdodrUQ4dMeDk+JEjK0V1BF3I6XVcezAI= X-Google-Smtp-Source: AGHT+IF5zd/9yv+5NftP+86LQyzKD3tldme+reqeIHS3yiMhYrMBJhCiVHsjnbNMqRTu0KMXRAVC8T/+Dya8oFVHzj4= X-Received: by 2002:a05:6402:5255:b0:5d4:75b:8ced with SMTP id 4fb4d7f45d1cf-5d81de39845mr171146a12.32.1734640933710; Thu, 19 Dec 2024 12:42:13 -0800 (PST) MIME-Version: 1.0 References: <95d1dc90-42f0-4026-aec1-8e21c5f2a205@aklaver.com> <9560200b-9de3-441b-b381-90c2fc4e78e3@aklaver.com> In-Reply-To: <9560200b-9de3-441b-b381-90c2fc4e78e3@aklaver.com> From: Renzo Dani Date: Thu, 19 Dec 2024 21:42:02 +0100 Message-ID: Subject: Re: Issue with pg_dump due to Schema OID Error To: Adrian Klaver Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000aab7930629a5900c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aab7930629a5900c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 =3D '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=3D# \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=3D# 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=E2=80=AFPM Adrian Klaver 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.klaver@aklaver.com > > --000000000000aab7930629a5900c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 a= dding the extension we use, one after one, and testing in between.

I found out that the problem appear immediately as so= on as I add the extension pg_stat_statements:

=

c= reate extension pg_stat_statements WITH SCHEMA public;<= /p>

alter system set shared_preload_libraries =3D 'pg_stat_= statements';


Can you ma= ybe test as well with this extension?
the other that I insta= lled before that are: pgcrypto and=C2=A0 pg_prewarm.

here the current installed one:

dbtest= =3D# \dx
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 List of installed extensions
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 Name =C2=A0 =C2=A0 =C2=A0 =C2=A0| Version | =C2=A0 Schema =C2=A0 | =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0Description =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
-= -------------------+---------+------------+--------------------------------= ----------------------------------------
=C2=A0pg_prewarm =C2=A0 =C2=A0 = =C2=A0 =C2=A0 | 1.2 =C2=A0 =C2=A0 | public =C2=A0 =C2=A0 | prewarm relation= data
=C2=A0pg_stat_statements | 1.11 =C2=A0 =C2=A0| public =C2=A0 =C2= =A0 | track planning and execution statistics of all SQL statements execute= d
=C2=A0pgcrypto =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | 1.3 =C2=A0 =C2=A0 = | public =C2=A0 =C2=A0 | cryptographic functions
=C2=A0plpgsql =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 1.0 =C2=A0 =C2=A0 | pg_catalog | PL/pgS= QL procedural language
(4 rows)

dbtest=3D# select version();
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0version =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0
-------------------------------------------------------------= -----------------------------------------------------
=C2=A0PostgreSQL 1= 7.2 reda build on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.3.0-6ubun= tu2~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=E2=80=AFPM Adrian Klaver <adrian.klaver@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 sa= me
>> problem.
>> The script do not rely now on any additional relation than the one= s
>> defined into the script.

I could not replicate using Ubuntu 22.04 and Postgres 16.6.

=C2=A0From your original post:

"I reproduced the problem on PostgreSQL versions 16.1 and 17.1."<= br>
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.klave= r@aklaver.com

--000000000000aab7930629a5900c--