| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PITR potentially broken in 9.2 |
| Date: | 2012-11-28 15:51:08 |
| Message-ID: | 241.1354117868@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 28.11.2012 06:27, Noah Misch wrote:
>> I observed a similar problem with 9.2. Despite a restore_command that failed
>> every time, startup from a hot backup completed. At the time, I suspected a
>> mistake on my part.
> I believe this was caused by this little typo/thinko:
Is this related at all to the problem discussed over at
http://archives.postgresql.org/pgsql-general/2012-11/msg00709.php
? The conclusion-so-far in that thread seems to be that an error
ought to be thrown for recovery_target_time earlier than the
backup stop time, but one is not getting thrown.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-11-28 20:31:19 | Re: PITR potentially broken in 9.2 |
| Previous Message | Andres Freund | 2012-11-28 14:38:40 | Re: PITR potentially broken in 9.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-11-28 17:04:45 | json accessors |
| Previous Message | Markus Wanner | 2012-11-28 15:45:51 | Re: Review: Extra Daemons / bgworker |