From: | Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp> |
---|---|
To: | ssinger_pg(at)sympatico(dot)ca |
Cc: | cedric(dot)villemain(dot)debian(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Online base backup from the hot-standby |
Date: | 2011-08-17 08:59:37 |
Message-ID: | 201108170900.p7H90CX9018760@ccmds32.silk.ntts.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Is there any way to tell from the WAL segments if they contain the full
> page data? If so could you verify this on the second slave when it is
> brought up? Or can you track this on the first slave and produce an
> error in either pg_start_backup or pg_stop_backup()
Sure.
I will make a patch with the way to tell from the WAL segments if they
contain the full page data.
> I see in xlog.h XLR_BKP_REMOVABLE, the comment above it says that this
> flag is used to indicate that the archiver can compress the full page
> blocks to non-full page blocks. I am not familiar with where in the code
> this actually happens but will this cause issues if the first standby is
> processing WAL files from the archive?
I confirmed the flag in xlog.c, so I seemed to only insert it in
XLogInsert(). I consider whether it is available.
--------------------------------------------
Jun Ishizuka
NTT Software Corporation
TEL:045-317-7018
E-Mail: ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp
--------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2011-08-17 09:02:17 | Re: [COMMITTERS] pgsql: Adjust total size in pg_basebackup progress report when reality |
Previous Message | Heikki Linnakangas | 2011-08-17 08:49:21 | Re: Enforcing that all WAL has been replayed after restoring from backup |