Re: Cannot pg_dump_all anymore...

From: E-BLOKOS <infos(at)e-blokos(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Cannot pg_dump_all anymore...
Date: 2025-03-19 02:17:22
Message-ID: 7248b50a-cf98-4169-a02d-f9a8f5e196ef@e-blokos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 3/18/2025 3:59 AM, Ron Johnson wrote:
> On Tue, Mar 18, 2025 at 5:14 AM E-BLOKOS <infos(at)e-blokos(dot)com> wrote:
>
> I got this error:
>
> pg_dump: error: query returned 0 rows instead of one: EXECUTE
> dumpBaseType('794978')
>
> any clue to solve it?
>
>
> PG version?
>
PG 17.4
> Whole command line, including all error messages?
>
>
setpriv su - postgres -c "pg_dumpall --no-comments -h /run/postgresql -p
5432 > out.sql"

--
E-BLOKOS

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sebastien Flaesch 2025-03-19 06:41:25 Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Previous Message E-BLOKOS 2025-03-19 02:16:23 Re: Cannot pg_dump_all anymore...