Re: changing port numbers so pgbouncer can read geoserver and postgres

Ok now I seem to have gotten it working by changing the store port numbers to
pgbouncer because its using port no 5432 and postgres is now using 6432.

So now it seems to be giving me the server details that is being used when
the map gets run:

pgbouncer=# show servers;
type | user | database | state | addr | port | local_addr |
local_port | connect_time | request_time | ptr | link
------+----------+----------+-------+-----------+------+------------+------------+---------------------+---------------------+----------+------
S | postgres | manifold | idle | 127.0.0.1 | 6432 | 127.0.0.1 |
62261 | 2013-11-08 15:08:37 | 2013-11-08 15:08:48 | 0197da20 |
S | postgres | manifold | idle | 127.0.0.1 | 6432 | 127.0.0.1 |
62259 | 2013-11-08 15:08:37 | 2013-11-08 15:08:47 | 0197d930 |
(2 rows)

and connections have gone down from 100 to 5 when I check on pgadmin for the
connections.

Is it because of putting the default pool size from 20 - 2 ( I was trying to
test something).

Is meant to show that its idle or that its being used on the server part on
the top

--
View this message in context: http://postgresql.1045698.n5.nabble.com/changing-port-numbers-so-pgbouncer-can-read-geoserver-and-postgres-tp5776631p5777468.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.