Re: BUG #17394: pg_dump: query returned 0 rows instead of one:

Hi Tom,

That works for me, Thanks alot.

Thanks,
Surya

On Fri, 4 Feb 2022 at 20:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> PG Bug reporting form <noreply(at)postgresql(dot)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
>