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/-.log what is the
log rotation policy of each logs.
use case: if i am writing a s
:53 AM:
>
> > From: Stephen Frost
> > To: Ajay Pratap
> > Cc: Postgres General
> > Date: 2019/10/11 08:51 AM
> > Subject: [EXTERNAL] Re: Pgbackrest backup is too slow
> >
> > Greetings,
> >
> > * Ajay Pratap (ajaypra...@ameyo.com) wrote:
>
##Arch
OS: Centos 7
PostgreSQL 10
pgbackrest 2.18
PAF: two nodes(primary and secondary ) with corosync and pacemaker
##Query
I am using pacemaker and corosync to setup two nodes High availability
cluster for postgreSQL 10. In the scenario I want to setup timely backup
with pgbackrest.
Using the _b
kept for backup /restore. Or any other
configuration?
My DB size is 500GB and increasing .
Regards,
Ajay
On Fri, Oct 11, 2019 at 6:20 PM Stephen Frost wrote:
> Greetings,
>
> * Ajay Pratap (ajaypra...@ameyo.com) wrote:
> > I have a Centos 7 server which runs Postgresql 1
for me to use it as it is.pgbackrest version is
2.18-1.rhel7.x86_64.
installed from pgdg yum repo.
Also I need to take a backup from the remote machine which would also
increase the overall runtime of backup/restore.
Thanks for the help in advance
Regards,
Ajay pratap
--
*Disclaimer:* The
Maybe postgresql (application) layer ping pong.
Enabling system wise timeouts can impact my whole setup including my web
app, thats why it is hard for me to configure them.
On Wed, Apr 17, 2019, 22:12 Francisco Olarte wrote:
> On Wed, Apr 17, 2019 at 4:49 PM Ajay Pratap
>
Correction: I meant when my java application dies postgres should break all
the connections that were associated with that peer.
On Wed, Apr 17, 2019, 19:59 Adrian Klaver wrote:
> On 4/17/19 5:39 AM, Ajay Pratap wrote:
> > Hello there,
> > I am using PostgreSQL 10.7 as the dat
client dies.
One of the methods is to configure TCP timeout but since this is very
impactful and hence unrealistic.
I was wounding how can out of the box PostgreSQL help me solve this.
May be like a ping pong service to check if client is still alive.
Thanks and regards,
Ajay Pratap,
Software Engineer
