> You're assuming that the only significant aspect of initdb's output that
can vary from run to run is the database system ID.
I prefer to call it "optimistic prediction". But yes. :)
> If you're lucky this technique will work, but it's not reliable and not
supported. You really need to take an
otheus uibk writes:
> I came up with an answer to the _second_ question (how do I do this from a
> new instance?).
> In the new instance directory:
> 1. Hack the system ID in the global/pg_control file to that of the original
> instance.
>1a. Use pg_controlinfo to get the hex version of the c
On Wed, Feb 17, 2016 at 9:16 AM, otheus uibk wrote:
> I came up with an answer to the _second_ question (how do I do this from a
> new instance?).
> [...]
> Again, this worked for me. What I want to be sure of is: does this really
> work?
>
I cannot definitively answer the question but it you
I came up with an answer to the _second_ question (how do I do this from a
new instance?).
In the new instance directory:
1. Hack the system ID in the global/pg_control file to that of the original
instance.
1a. Use pg_controlinfo to get the hex version of the control id:
$ pg_controldata
I'm looking for answers to this question, but so far haven't turned up a
usable answer. Perhaps I'm asking it the wrong way.
I want to replay the xlogs from the beginning of time up until a particular
time. The problem is, the time is before the first base backup. But I have
all the xlogs since th
