On Thu, Aug 12, 2010 at 5:54 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > I wrote: >> I wonder if the problem is not so much libpqwalreceiver as the >> walreceiver process. Maybe an ordinary backend process does some >> prerequisite initialization that walreceiver is missing. Hard to >> guess what, though ... I can't think of anything dlopen() depends on >> that should be under our control. > > Actually, that idea is easily tested: try doing > LOAD 'libpqwalreceiver'; > in a regular backend process. Alanoly, is this something you can try? > If that still crashes, it might be useful to truss or strace the backend > while it runs the command, and compare that to the trace of > LOAD 'dblink'; And if necessary, this too? Thanks for your help debugging this.... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
