From: | Éric de la Musse <eric901(at)pouik(dot)org> |
---|---|
To: | pgsql-fr-generale(at)postgresql(dot)org |
Subject: | Restauration d'une sauvegarde PITR avec recovery_target_time |
Date: | 2016-06-18 18:05:28 |
Message-ID: | 20160618200528.25cfb78a@archie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-fr-generale |
Bonsoir,
j'ai un souci avec le processus de restauration PITR et plus
particulièrement avec le sens/fonctionnement du paramètre
recovery_target_time.
Si je positionne celui-ci sur '2016-06-18 03:00 Europe/Paris' et que je
lance la récupération à partir d'un backup de base fait à '2016-06-18
02:00 Europe/Paris' j'ai le retour ci-dessous
========
LOG: database system was interrupted; last known up at 2016-06-18
00:00:01 GMT
LOG: creating missing WAL directory "pg_xlog/archive_status"
LOG: starting point-in-time recovery to 2016-06-18 03:00:00+02
LOG: restored log file "000000010000001500000077" from archive
LOG: redo starts at 15/77000098
LOG: consistent recovery state reached at 15/770000C0
LOG: restored log file "000000010000001500000078" from archive
LOG: restored log file "000000010000001500000079" from archive
... blah blah ...
LOG: restored log file "00000001000000150000009A" from archive
LOG: restored log file "00000001000000150000009B" from archive
LOG: recovery stopping before commit of transaction 1523, time
2016-06-18 05:00:02.655446+02
LOG: redo done at 15/9B0AA980
========
Je comprends la 1ère ligne : 00:00:00 GMT est bien l'heure de la
sauvegarde de base.
La 3ème ("starting point-in-time recovery to 2016-06-18 03:00:00+02" )
est bien ce que je demande.
Mais la restauration s'effectue jusqu'à 2016-06-18 05:00:02.655446+02
...soit 2 heures de plus que l'objectif fixé.
Je me suis dis que le type de recovery_target_time étant
indiqué dans la doc comme de type timestamp et non timestamp with time
zone il fallait positionner le paramètre sur une heure UTC soit
'2016-06-18 01:00' ici mais le résultat est tout aussi décevant,
j'ai toujours 2 heures de trop (voir ci-dessous).
Merci de vos lumières.
========
LOG: database system was interrupted; last known up at 2016-06-18
00:00:01 GMT
LOG: creating missing WAL directory "pg_xlog/archive_status"
LOG: starting point-in-time recovery to 2016-06-18 01:00:00+00
LOG: restored log file "000000010000001500000077" from archive
LOG: redo starts at 15/77000098
LOG: consistent recovery state reached at 15/770000C0
LOG: restored log file "000000010000001500000078" from archive
LOG: restored log file "000000010000001500000079" from archive
... blah blah ...
LOG: restored log file "00000001000000150000009A" from archive
LOG: restored log file "00000001000000150000009B" from archive
LOG: recovery stopping before commit of transaction 1523, time
2016-06-18 03:00:02.655446+00
LOG: redo done at 15/9B0AA980
========
--
Éric de la Musse
--
Envoi via la liste pgsql-fr-generale (pgsql-fr-generale(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2016-06-18 20:27:14 | Re: Restauration d'une sauvegarde PITR avec recovery_target_time |
Previous Message | Cédric Villemain | 2016-06-17 15:39:02 | Re: replication synchrone |