gdb is not available on this machine. Neither which or locate could find it. The servers we're given are truly, shockingly, stripped down models.
At this point, I believe my best course of action is to twist some sys admin arms and get a properly installed PostgreSQL on this machine. Even if I manage to get the mirror working with the current install, there's a real risk something bad will happen. I can't trust this source built version.
Sigh
Thanks again for your help.
-- Richard Brosnahan
On Dec 15, 2016, at 01:00 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Richard Brosnahan <broz@xxxxxxx> =?utf-8?B?UmU6IFtHRU5FUkFMXSBQb3N0Z3JlU1FMIG1pcnJvcmluZyBmcm9tIFJQTSBp?= =?utf-8?B?bnN0YWxsIHRvIFNvdXJjZSBpbnN0YWxs?= writes:The slave:$ pg_controldata --versionpg_controldata (PostgreSQL) 9.4.1$ echo $PGDATA/apps/database/postgresql-data$ pg_controldata $PGDATAWARNING: Calculated CRC checksum does not match value stored in file.Either the file is corrupt, or it has a different layout than this programis expecting. The results below are untrustworthy.Segmentation fault (core dumped)
Wow --- a core dump in pg_controldata is *really* unexpected, since it's
just printing some scalar fields. I can easily believe garbage out, but
a crash is harder. I'm beginning to think that there's something wrong
with your hand-rolled build, though I have no idea what.
Can you get a stack trace out of that? Should be enough to do
$ gdb path/to/pg_controldata
gdb> run /apps/database/postgresql-data
(wait for it to report segfault)
gdb> btUnderstood that it's way easier to do the mirroring when the directory paths agree. In my case, I can't line them up, due to restrictions.
That doesn't seem to be your problem, at least not yet.
regards, tom lane
