pgbackrest concerns and doubts.

From: Ajay Pratap <ajaypratap(at)ameyo(dot)com>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: pgbackrest concerns and doubts.
Date: 2019-12-02 06:52:13
Message-ID: CABi=8qwKob2V8tBV9sq-RfY7g-JRQEFfOb-XJXPv5MswZV8fDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,
I am using Postgresql 10 and pgbackrest 2.18 version on centos 7.6
I have few doubts regard pgbackrest.
a) what is the log rotation policy for pgbackrest logs. I see it logs on
default path /var/log/pgbackrest/<stanzaname>-<operation>.log what is the
log rotation policy of each logs.
use case: if i am writing a script to parse the logs and gatter some info,
i should be aware of log rotation or if logs doesn't rotate a single file
could be huge to parse.
Or should I simply use *logrotate*

b) since pgbackrest takes physical backup,
what are the impact if I upgrades minor postgres version(10.5 to 10.10)
and impact on postgres major version(10.10 to 12.X)

Thanks and regards,

--

*Disclaimer:* The information in this communication is confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed and others authorized to
receive it. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking action in reliance of
the contents of this information is strictly prohibited and may be
unlawful. Drishti is neither liable for the improper, incomplete
transmission of the information contained in this communication nor any
delay in its receipt. The communication is not intended to operate as an
electronic signature under any applicable law. Drishti assumes no
responsibility for any loss or damage resulting from the use of e-mails.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laura Smith 2019-12-02 11:10:44 Conditional return of aggregated data
Previous Message David Wheeler 2019-12-02 06:41:30 Connection terminated but client didn't realise