On Wed, Apr 27, 2016 at 12:09 PM, Steve Crawford
wrote:
> On Wed, Apr 27, 2016 at 1:29 AM, Francisco Olarte
> wrote:
>>
>> Hi Cal:
>>
>> On Tue, Apr 26, 2016 at 5:20 PM, Cal Heldenbrand wrote:
>> ...
>> > 2) %M vs shell call
>> > %M on when connected to the local machine displays the string "[l
On Wed, Apr 27, 2016 at 12:09 PM, Steve Crawford
wrote:
> On Wed, Apr 27, 2016 at 1:29 AM, Francisco Olarte
> wrote:
>>
>> Hi Cal:
>>
>> On Tue, Apr 26, 2016 at 5:20 PM, Cal Heldenbrand wrote:
>> ...
>> > 2) %M vs shell call
>> > %M on when connected to the local machine displays the string "[l
>
> I don't see anything obvious. Putting this back on the list, where
> it should have stayed all along. Maybe someone else has an idea;
> I've only seen such behavior when there were archiving problems
> which were showing up in the server log.
>
> -Kevin
>
>
> --
Perhaps it cannot delete old log
El may 3, 2011 5:59 p.m., "John R Pierce" escribió:
>
> On 05/03/11 3:07 PM, dabicho wrote:
>>
>>
>> For restoring a database from wal files, if I omit a target on the
recovery.conf file, can I make it so the database continues the time line
instead of starting
For restoring a database from wal files, if I omit a target on the
recovery.conf file, can I make it so the database continues the time line
instead of starting one?
Or is there a tool to pick the most recent time line from a bunch of wal
files?
thankyou.
