From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Quentin Hartman <qhartman(at)direwolfdigital(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Streaming replication slave crash |
Date: | 2013-03-29 16:50:32 |
Message-ID: | 27199.1364575832@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Quentin Hartman <qhartman(at)direwolfdigital(dot)com> writes:
> On Fri, Mar 29, 2013 at 10:37 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What process did you use for setting up the slave?
> I used an rsync from the master while both were stopped.
If the master was shut down cleanly (not -m immediate) then the bug fix
I was thinking about wouldn't explain this. The fact that the panic
didn't recur after restarting seems to void that theory as well. I'm
not sure what to make of that angle.
Can you determine which table is being complained of in the failure
message, ie, what has relfilenode 63370 in database 63229? If so it
would be interesting to know what was being done to that table on the
master.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Quentin Hartman | 2013-03-29 17:10:41 | Re: Streaming replication slave crash |
Previous Message | Quentin Hartman | 2013-03-29 16:43:09 | Re: Streaming replication slave crash |