From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alanoly Andrews <alanolya(at)invera(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] postgres 9.0 crash when bringing up hot standby |
Date: | 2010-08-13 15:11:19 |
Message-ID: | AANLkTinw-_jp5erj0Oa=WbMdtOpvHX9vpWWTmcyofokr@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On Thu, Aug 12, 2010 at 5:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Ricardo Bayley | 2010-08-13 21:08:15 | NEW + tableOID |
Previous Message | Gnanakumar | 2010-08-13 13:24:02 | SQL statements not printed in pgpool log |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-08-13 16:00:32 | Re: patch: utf8_to_unicode (trivial) |
Previous Message | Robert Haas | 2010-08-13 15:10:23 | Re: typos in HS source code comment |