Re: Streaming replication, loose ends
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Boszormenyi Zoltan <zb@cybertec.at>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-01-15T17:03:18Z
Lists: pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > Tom Lane wrote: >> I'm actually fairly uncomfortable with the notion that something buried >> deep within the src/backend tree is going to reach over and cause libpq >> to get built. Maybe the real answer is that you put walreceiver in the >> wrong place, and it ought to be under src/bin/. > That feels even more wrong to me. Walreceiver is a postmaster > subprocess, tightly integrated with the rest of the backend. [ shrug... ] pg_dump, to take one example, is considerably more "tightly integrated" with the backend than walreceiver is. regards, tom lane