On 3/18/2025 3:59 AM, Ron Johnson wrote:
On Tue, Mar 18, 2025 at 5:14 AM E-BLOKOS 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 err
On 3/18/2025 5:49 AM, Greg Sabino Mullane wrote:
First figure out which database is having that issue, by using pg_dump
--schema-only on each database in turn. Then run this SQL on the
database giving the error to see if the type exists, or what is nearby:
select oid, typname, typtype, typnam
Hi,
On 3/19/2025 7:08 AM, Greg Sabino Mullane wrote:
On Wed, Mar 19, 2025 at 10:02 AM E-BLOKOS wrote:
is it possible a crash happened with a VACUUM and a machine reboot
in same time?
More likely to be a problem with pg_repack. Please tell us the exact
versions of pg_repack and Post
On Wed, Mar 19, 2025 at 10:02 AM E-BLOKOS wrote:
> is it possible a crash happened with a VACUUM and a machine reboot in same
> time?
>
More likely to be a problem with pg_repack. Please tell us the exact
versions of pg_repack and Postgres in use here.
Cheers,
Greg
--
Crunchy Data - https://w
On 3/18/2025 5:49 AM, Greg Sabino Mullane wrote:
First figure out which database is having that issue, by using pg_dump
--schema-only on each database in turn. Then run this SQL on the
database giving the error to see if the type exists, or what is nearby:
select oid, typname, typtype, typnam
On Tue, Mar 18, 2025 at 5:14 AM E-BLOKOS 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?
Whole command line, including all error messages?
--
Death to , and butter sauce.
Don't boil m
First figure out which database is having that issue, by using pg_dump
--schema-only on each database in turn. Then run this SQL on the database
giving the error to see if the type exists, or what is nearby:
select oid, typname, typtype, typnamespace::regnamespace from pg_type where
oid <= 794978
