From: | Charles Schultz <sacrophyte(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Questions on recovery situations (not urgent) |
Date: | 2024-06-11 11:22:35 |
Message-ID: | CAPZQniV7AbYEFx_y8AOG81NRfE724SNCk1Pxn=0+iAyb09g77w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
It turns out that we are using TDE (which I knew, but I assumed pg_waldump
was decrypting - bad assumption). It took a few tries, but I finally
figured out how to get pg_waldump to work with the decrypt flags.
Thanks for the feedback!
On Mon, Jun 10, 2024 at 8:37 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Mon, 2024-06-10 at 13:41 -0500, Charles Schultz wrote:
> > On Wed, May 29, 2024 at 10:05 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
> > > Did you compress the files? If yes, you have to uncompress them
> before feeding them
> > > to "pg_waldump".
> >
> > We do use compression (wal_compression="on"), which looks to default to
> pglz.
> > How might I decompress them? I tried gunzip in several iterations, but
> no dice.
>
> That will compress full-page images *within* the WAL segment, but not the
> file
> itself. The file should still have the regular size.
>
> Perhaps your archiver truncated the file somehow.
>
> Yours,
> Laurenz Albe
>
--
Charles Schultz
From | Date | Subject | |
---|---|---|---|
Next Message | SOzcn | 2024-06-11 21:15:17 | Index - Concurrently Method |
Previous Message | Laurenz Albe | 2024-06-11 01:37:29 | Re: Questions on recovery situations (not urgent) |