From: Tom Lane <tgl@sss.pgh.pa.us>
To: suryasp1010@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17394: pg_dump: query returned 0 rows instead of one:
Date: Fri, 04 Feb 2022 09:47:50 -0500
Message-ID: <388724.1643986070@sss.pgh.pa.us> (raw)
In-Reply-To: <17394-136ca1f54be097f9@postgresql.org>
References: <17394-136ca1f54be097f9@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> pg_dump: query returned 0 rows instead of one:
> SELECT proretset, prosrc, probin, pg_catalog.pg_get_function_arguments(oid)
> AS funcargs,pg_catalog.pg_get_function_identity_arguments(oid) AS funciargs,
> pg_catalog.pg_get_function_result(oid) AS funcresult,
> array_to_string(protrftypes, ' ') AS protrftypes, prokind, provolatile,
> proisstrict, prosecdef, proleakproof, proconfig, procost, prorows,
> proparallel, (SELECT lanname FROM pg_catalog.pg_language WHERE oid =
> prolang) AS lanname FROM pg_catalog.pg_proc WHERE oid =
> '1046460'::pg_catalog.oid
If it's repeatable, maybe reindexing pg_proc would help.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, suryasp1010@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17394: pg_dump: query returned 0 rows instead of one:
In-Reply-To: <388724.1643986070@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox