On Fri, 2023-01-13 at 11:23 +, Zwettler Markus (OIZ) wrote:
> > -Ursprüngliche Nachricht-
> > Von: Laurenz Albe
> > Gesendet: Freitag, 13. Januar 2023 11:25
> > An: Zwettler Markus (OIZ) ; pgsql-
> > gene...@lists.postgresql.org
> > Betreff: R
> -Ursprüngliche Nachricht-
> Von: Laurenz Albe
> Gesendet: Freitag, 13. Januar 2023 11:25
> An: Zwettler Markus (OIZ) ; pgsql-
> gene...@lists.postgresql.org
> Betreff: Re: AW: [Extern] Re: postgres restore & needed history files
>
> On Thu, 2023-01-12 at
On Thu, 2023-01-12 at 16:50 +, Zwettler Markus (OIZ) wrote:
> What would you do in case of a disaster when all history files in pg_wal are
> gone
> and also deleted in the backup due to the backup retention?
Easy. Take a new base backup immediately and don't try to restore a backup
that was
On 1/12/23 10:50, Zwettler Markus (OIZ) wrote:
[snip]
What would you do in case of a disaster when all history files in pg_wal are
gone and also deleted in the backup due to the backup retention?
Yet another reason why you should not roll your own PITR backup solution.
Use something like pgB
> -Ursprüngliche Nachricht-
> Von: Laurenz Albe
> Gesendet: Freitag, 6. Januar 2023 06:28
> An: Zwettler Markus (OIZ) ; pgsql-
> gene...@lists.postgresql.org
> Betreff: [Extern] Re: postgres restore & needed history files
>
> On Tue, 2023-01-03 at 16:03 +,
> On Jan 5, 2023, at 21:28, Laurenz Albe wrote:
>
> On Tue, 2023-01-03 at 16:03 +, Zwettler Markus (OIZ) wrote:
>> We are using a DIY Postgres backup:
>> ---
>> psql -c "select pg_start_backup ('Full');"
>> save -s "${NSR_SERVER}" -g "${NSR_POOL}" "${PGDATA}"
>> psql -c "select pg_stop_bac
On Tue, 2023-01-03 at 16:03 +, Zwettler Markus (OIZ) wrote:
> We are using a DIY Postgres backup:
> ---
> psql -c "select pg_start_backup ('Full');"
> save -s "${NSR_SERVER}" -g "${NSR_POOL}" "${PGDATA}"
> psql -c "select pg_stop_backup();"
> ---
> The pg_wal directory is not saved with it beca
