| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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-12 21:40:20 |
| Message-ID: | 6546.1281649220@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Per off-list discussion with Alanoly, we've determined the following:
> dblink was compiled with the same flags as libpqwalreciever
> dblink works
> libpqwalreceiver crashes
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-12 21:54:49 | Re: [HACKERS] postgres 9.0 crash when bringing up hot standby |
| Previous Message | Robert Haas | 2010-08-12 20:37:50 | Re: [HACKERS] postgres 9.0 crash when bringing up hot standby |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-12 21:54:49 | Re: [HACKERS] postgres 9.0 crash when bringing up hot standby |
| Previous Message | Alvaro Herrera | 2010-08-12 21:29:25 | Re: including backend ID in relpath of temp rels - updated patch |