[pgpool-general: 1103] Re: Just installed pgpool in production

[Lonni J Friedman]

++
This is a very bad idea, as if your database server dies, you loose
pgpool too, which effectively negates the point of running pgpool.

On Mon, Oct 22, 2012 at 8:20 AM, Wolf Schwurack <wolf at uen.org> wrote:
> Ok not sure why you want to run both on the same physical machine.
>
>
>
> Wolf
>
>
>
> From: Mark Steben [mailto:mark.steben at drivedominion.com]
> Sent: Monday, October 22, 2012 8:55 AM
> To: Wolf Schwurack
> Cc: pgpool-general at pgpool.net
> Subject: Re: [pgpool-general: 1096] Just installed pgpool in production
>
>
>
> The pgpool server and the database server reside on the same physical
> machine.
> pgpool runs on port 5432  and the database runs on 5433.  When I run pg_top
> -p 5433
> I get the same results as querying on 5432.
>
> On Mon, Oct 22, 2012 at 9:17 AM, Wolf Schwurack <wolf at uen.org> wrote:
>
> Are you running pg_top from the pgpool server or postgres server? Try
> running pg_top on the postgres server
>
>
>
> Wolf
>
>
>
> From: Mark Steben [mailto:mark.steben at drivedominion.com]
> Sent: Monday, October 22, 2012 7:12 AM
> To: Wolf Schwurack; pgpool-general at pgpool.net
> Subject: Re: [pgpool-general: 1096] Just installed pgpool in production
>
>
>
> Hi Wolf,  thanks for getting back to me so quickly.
>
> For me, pg_top also shows the localhost 127.0.0.1 of
> all connections managed by pg_pool:
>
>    PID USERNAME PRI NICE  SIZE   RES STATE   TIME   WCPU    CPU COMMAND
>  6171 postgres  16    0 2685M 1041M run    12:52 63.14% 67.78% postgres:
> mavmail mavmail 127.0.0.1(54941) SELECT
>  9756 postgres  15    0 2691M  332M sleep   0:00  1.50% 14.15% postgres:
> mavmail mavmail 127.0.0.1(40242) idle
>  3870 postgres  15    0 2687M 2590M sleep  88:52  4.63% 10.17% postgres:
> prime prime_production 127.0.0.1(35780) idle
>  7103 postgres  15    0 2692M  779M sleep   0:06  2.24%  8.77% postgres:
> mavmail mavmail 127.0.0.1(39860) idle
>  7419 postgres  15    0 2705M  500M sleep   0:27  0.50%  5.98% postgres:
> mavmail mavmail 127.0.0.1(39984) idle
>
> On Mon, Oct 22, 2012 at 9:04 AM, Wolf Schwurack <wolf at uen.org> wrote:
>
> Have you tried using pg_top? It shows the ip connects of each process.
>
>
>
> Wolf
>
>
>
> From: pgpool-general-bounces at pgpool.net
> [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Mark Steben
> Sent: Monday, October 22, 2012 6:47 AM
> To: pgpool-general at pgpool.net
> Subject: [pgpool-general: 1096] Just installed pgpool in production
>
>
>
> Good morning,
>
> We are running with pgpool for our second business day today.
> I was wondering if there is a way to capture the i/p connection of the
> originating server, as pgpool now manages most of our connections and
> emits a local (127.0.0.1) I/P address.  We would prefer to trace back to
> the originating server(s) for debug purposes.
>
> We are currently running postgres 8.3.15 and pgpool 3.2.0.