On 27.12.2012 12:06, Heikki Linnakangas wrote:
On 23.12.2012 15:33, Fujii Masao wrote:
On Fri, Dec 21, 2012 at 9:54 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
Yes, this should be backpatched to 9.2. I came up with the attached.
In this patch, if '-X stream' is specified in
On Wed, Jan 2, 2013 at 1:55 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
If you take a backup with pg_basebackup -X fetch, and the timeline
switches while the backup is taken, you currently get an error like
requested WAL segment 0001000C has already been removed.
To
On 23.12.2012 15:33, Fujii Masao wrote:
On Fri, Dec 21, 2012 at 9:54 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
Yes, this should be backpatched to 9.2. I came up with the attached.
In this patch, if '-X stream' is specified in pg_basebackup, the timeline
history files are not
On Fri, Dec 21, 2012 at 9:54 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
Yes, this should be backpatched to 9.2. I came up with the attached.
In this patch, if '-X stream' is specified in pg_basebackup, the timeline
history files are not backed up. We should change pg_backup background
On 17.12.2012 18:58, Magnus Hagander wrote:
On Mon, Dec 17, 2012 at 5:19 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Heikki Linnakangashlinnakan...@vmware.com writes:
I'm not happy with the fact that we just ignore the problem in a backup
taken from a standby, silently giving the user a backup
On Friday, December 21, 2012 6:24 PM Heikki Linnakangas wrote:
On 17.12.2012 18:58, Magnus Hagander wrote:
On Mon, Dec 17, 2012 at 5:19 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Heikki Linnakangashlinnakan...@vmware.com writes:
I'm not happy with the fact that we just ignore the problem in a
On 18 December 2012 00:53, Tom Lane t...@sss.pgh.pa.us wrote:
Simon Riggs si...@2ndquadrant.com writes:
On 17 December 2012 14:16, Heikki Linnakangas hlinnakan...@vmware.com
wrote:
I also wonder if pg_basebackup should
include *all* timeline history files in the backup, not just the latest
On Tue, Dec 18, 2012 at 8:09 PM, Simon Riggs si...@2ndquadrant.com wrote:
On 18 December 2012 00:53, Tom Lane t...@sss.pgh.pa.us wrote:
Simon Riggs si...@2ndquadrant.com writes:
On 17 December 2012 14:16, Heikki Linnakangas hlinnakan...@vmware.com
wrote:
I also wonder if pg_basebackup should
Fujii Masao masao.fu...@gmail.com writes:
On Tue, Dec 18, 2012 at 8:09 PM, Simon Riggs si...@2ndquadrant.com wrote:
What I'm saying is that the new history file is created from the old
one, so the latest file includes all the history as a direct copy. The
only thing new is one line of
pg_basebackup -x is supposed to include all the required WAL files in
the backup, so that you have everything needed to restore a consistent
database. However, it's not including the timeline history files.
Usually that's not a problem because normally you don't need to follow
any old
Heikki Linnakangas hlinnakan...@vmware.com writes:
I'm not happy with the fact that we just ignore the problem in a backup
taken from a standby, silently giving the user a backup that won't start
up. Why not include the timeline history file in the backup?
+1. I was not aware that we
On Mon, Dec 17, 2012 at 5:19 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
I'm not happy with the fact that we just ignore the problem in a backup
taken from a standby, silently giving the user a backup that won't start
up. Why not include the
On 17 December 2012 14:16, Heikki Linnakangas hlinnakan...@vmware.com wrote:
I'm not happy with the fact that we just ignore the problem in a backup
taken from a standby, silently giving the user a backup that won't start up.
That's spooky. I just found a different issue with prmotion during
Simon Riggs si...@2ndquadrant.com writes:
On 17 December 2012 14:16, Heikki Linnakangas hlinnakan...@vmware.com wrote:
I also wonder if pg_basebackup should
include *all* timeline history files in the backup, not just the latest one
strictly required to restore.
Why? the timeline history
14 matches
Mail list logo
