public inbox for [email protected]
help / color / mirror / Atom feedFrom: E-BLOKOS <[email protected]>
To: [email protected]
Subject: Re: Cannot pg_dump_all anymore...
Date: Wed, 19 Mar 2025 07:26:24 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKAnmm+TzEXtxAeJkrOzhOmDoLrxC0bznpe+HGAzAM+EXnkMeA@mail.gmail.com>
References: <[email protected]>
<CAKAnmmJ=OupUu_4N3nQWYAfwCN6aT4s1PKQypHmpPLnX5Bz6qg@mail.gmail.com>
<[email protected]>
<CAKAnmm+TzEXtxAeJkrOzhOmDoLrxC0bznpe+HGAzAM+EXnkMeA@mail.gmail.com>
Hi,
On 3/19/2025 7:08 AM, Greg Sabino Mullane wrote:
> On Wed, Mar 19, 2025 at 10:02 AM E-BLOKOS <[email protected]> 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.
>
>
PG 17.4
pg_repack last git
thanks
David
--
E-BLOKOS
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Cannot pg_dump_all anymore...
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox