Does any of this help this is the config file i get when I type in show
config in the pgbouncer admin console:
pgbouncer=# show config;
key| value
| changeable
---+
has it got to do with the DNS I have checked on the admin consol and a
recieved this:
pgbouncer=# show dns_hosts;
hostname | ttl | addrs
--+-+---
(0 rows)
pgbouncer=# show dns_zones;
zonename | serial | count
--++---
(0 rows)
Not to sure if this helps.
-
Why don't you try adding layers one by one?
1) Ensure you can connect to PostgreSQL from psql client (on another
machine)
2) Configure pgbouncer
3) See if you can connect from psql > pgbouncer > PostgreSQL
Check the data in pgbpuncer and PostgreSQL (number of sessions, idle
connections etc). You co
everytime I change something it seems when i type in show servers in the
admin console, it keeps showing 0 rows.
I have gone back and forth several time trying to get this thing sorted out
nut to no avail i keep getting the same message.
--
View this message in context:
http://postgresql.10456
Again, this output indicates that pgbouncer is not connecting to postgres
server.
Regards,
Igor Neyman
On Thu, Oct 31, 2013 at 11:02 AM, si24 wrote:
> I don't know if this will help in terms of my problem?
>
> this came from the admin pgbouncer console.
>
>
>
> pgbouncer=# show servers;
> typ
On 01/11/2013 09:46, si24 wrote:
So should I rather change the 6432 to 5432 like the postgresql port or 8080
like the geoserver tomcat port.
Yes, you could do like this... but have to change psql server's port too
... to other than 5432... and tell pgbouncer to which port connect to
postgresq
So should I rather change the 6432 to 5432 like the postgresql port or 8080
like the geoserver tomcat port.
Geoserver is on 8080 and reads all the tables that postgres has cause you
need to add the port no that postgres is on to be able for it read the
tables.
--
View this message in context:
On 01/11/2013 09:07, si24 wrote:
geoserver uses the same port number as tomcat does which 8080 as the moment
should I change it to something else?
postgres uses 5432(default port number to postgresql) and pgbouncer uses
6432(default port number given to pgbouncer)
Am I missed something or you
geoserver uses the same port number as tomcat does which 8080 as the moment
should I change it to something else?
postgres uses 5432(default port number to postgresql) and pgbouncer uses
6432(default port number given to pgbouncer)
--
View this message in context:
http://postgresql.1045698.n5.
On 10/31/2013 10:02 AM, si24 wrote:
I don't know if this will help in terms of my problem?
this came from the admin pgbouncer console.
pgbouncer=# show pools;
database | user| cl_active | cl_waiting | sv_active | sv_idle |
sv_used| sv_tested | sv_login | maxwait
---+--
On czw, paź 31, 2013 at 07:25:21 -0700, si24 wrote:
> Can some one please give me a bit more of a better explanation on how exactly
> the pgbouncer works as I am now lost.
>
> I'm not sure if it is pooling the connections cause surely if its not being
> used the connections should go down not up i
si24 wrote
> Can some one please give me a bit more of a better explanation on how
> exactly the pgbouncer works as I am now lost.
Working from theory here but:
Pool (PGBouncer) Connections: 1
PostgreSQL Connections: 1
Container Threads: 2 [A, B]
Thread A: get connection -> OK
Thread B: get conn
On 10/31/2013 7:38 AM, Adam Brusselback wrote:
If it is from your app to PGBouncer, that sounds strange, and like the
app is not properly releasing connections as it should. If it is from
PGBouncer to PostgreSQL, that sounds normal. I haven't used
PGBouncer, but i've used other connection p
For where you are measuring, everything looks normal to me.
Your application will make connections to the pooler as needed, and the
pooler will assign the application connection to a database connection it
has available in it's pool. This gets rid of the overhead of creating a
brand new connecti
I don't know if this will help in terms of my problem?
this came from the admin pgbouncer console.
pgbouncer=# show pools;
database | user| cl_active | cl_waiting | sv_active | sv_idle |
sv_used| sv_tested | sv_login | maxwait
---+---+---++---+
I use a check in postgres to give the active connections being used.
But what happens if the connection pooler goes all the way to 100 for
example and say that 100 is your postgres maximum connections at the time. I
know I can change the maximum connections in postgres but am not to sure on
the ri
I'm not a 100% sure but when i type : select count (*) from pg_stat_activity;
in postgres it give me the a number be 3 or 75 or higher depending on what
is runnung at the time if its the webpage with the map or just postgres
itself.
I had thought that the client connections to PgBouncer and pool c
Where are you measuring the connections? From your app to PGBouncer, or
from PGBouncer to PostgreSQL?
If it is from your app to PGBouncer, that sounds strange, and like the app
is not properly releasing connections as it should. If it is from
PGBouncer to PostgreSQL, that sounds normal. I haven'
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of si24
> Sent: Thursday, October 31, 2013 10:25 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Explanantion on pgbouncer please
>
> Can some one please give
19 matches
Mail list logo
