Re: Backup history file should be replicated in Streaming Replication?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Backup history file should be replicated in Streaming Replication?
Date: 2009-12-22 21:14:27
Message-ID: 1882.1261516467@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> I think we could get away without the backup history file altogether.

Hmmm ... actually I was confusing these with timeline history files,
which are definitely not something we can drop. You might be right
that the backup history file could be part of WAL instead. On the other
hand, it's quite comforting that the history file is plain ASCII and can
be examined without any special tools. I'm -1 for removing it, even
if we decide to duplicate the info in a WAL record.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aidan Van Dyk 2009-12-22 21:17:15 Re: Backup history file should be replicated in Streaming Replication?
Previous Message Tom Lane 2009-12-22 21:01:42 Re: Possible patch for better index name choosing