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, inc
imit 3;
oid | typname | typtype | typnamespace
++-+--
794970 | log_17167 | c | repack
794969 | _log_17167 | b | repack
794966 | pk_17167 | c | repack
(3 rows)
Arggh it's repack 🙁
I have no clue how to repair repack
--
E-BLOKOS
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
ixed it with:
SELECT * FROM pg_depend WHERE objid IN (794964, 794968);
DELETE FROM pg_depend WHERE objid IN (794964, 794968);
systemctl restart postgresql
is it possible a crash happened with a VACUUM and a machine reboot in
same time?
--
E-BLOKOS
I got this error:
pg_dump: error: query returned 0 rows instead of one: EXECUTE
dumpBaseType('794978')
any clue to solve it?
thanks
David
d Oracle are mostly maintaining XFS updates, and I didn't see
anything saying it's not mainained actively,
especially when they offering many solutions with XFS as default
--
E-BLOKOS
the legacy issues associated with xfs are long gone ?
XFS is indeed for me the most stable and performant for postgresql
today. EXT4 was good too, but less performant.
--
E-BLOKOS
ime of the
snapshot in order to reach consistency).
In the end though, really, it's much, much, much better to use a proper
backup and archiving tool that's written specifically for PG than to try
and roll your own, using snapshots or not.
Thanks,
Stephen
what about BTRFS since it's the successor of ZFS?
--
E-BLOKOS
