| From: | Derrick Rice <derrick(dot)rice(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Yaroslav Tykhiy <yar(at)barnet(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Warm Standby and resetting the primary as a standby |
| Date: | 2010-08-23 21:51:22 |
| Message-ID: | AANLkTikPONLBc7QKJyt0tdhbhfWkWZe+guydGqbGZmTn@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 23, 2010 at 5:45 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
> Sorry, I don't know. I think the timelines are only there for safety if
> you have to fall back to the previous timeline, and to prevent timeline
> mixing.
Thanks for the helpful answers.
Two follow up questions which, if they can be answered, will save some time
before I go testing random theories.
Is there a way to bump a database up a timeline version without specifying
the exact timeline version of interest? Apparently doing a rebase from a
database which has incremented its own timeline from doing a recovery does
at least this.
Is it possible to interpret the requested file and ignore the timeline
digits and provide a file from some other timeline? Or is the timeline mean
more than just the file name?
Derrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-08-23 22:03:22 | Re: Warm Standby and resetting the primary as a standby |
| Previous Message | Bruce Momjian | 2010-08-23 21:45:05 | Re: Warm Standby and resetting the primary as a standby |