Hi Oliver,
Il 12/07/2013 04:07, Wells Oliver ha scritto:
I ran:
pg_ctlcluster 9.1 main start
Received:
The PostgreSQL server failed to start. Please check the log output.
But, hey, in /var/log/postgresql, there was absolutely no logging.
Nothing. After some googling, I tried:
usr/lib/post
I was recently asked how long it takes for postgres (or in my case
pgbouncer) to create a database connection and could not find a way within
postgres logging or psql to report this information.
I came across depesz's great article on pgbouncer utilizing tcpdump:
http://www.depesz.com/2012/12/02/w
On Jul 12, 2013, at 9:00 AM, Mike Broers wrote:
> Is there something I am overlooking in postgres logging or psql client
> switches that would make this information available or am I stuck with lower
> level tools?
Well, if you want to log how long pgbouncer takes to hand out a connection from
BTW, just for the heck of it, I decided to try it out on my dev system (several
year old 17" MacBook Pro, meaning core i7 processor), PostgreSQL 9.2, pgbouncer
1.5. So, connecting via libpq to postgres directly takes 2-3 ms, connecting to
pgbouncer takes typically 70-150 us, with the occasional
On Jul 12, 2013, at 9:59 AM, Mike Broers wrote:
> Thanks, did you use tcpdump to determine that? I'm happy to learn a new tool
> (to me), but wanted to make sure I wasnt overlooking something at my disposal
> within postgres.
When I said "connecting via libpq" I meant I inserted timers in some
Alright but what's odd to me is that it's a standard out of the box ubuntu
configuration, meaning:
log_destination is 'stderr'
logging_collector is on
log_directory is /var/log/postgresql/
log_filename is postgresql-%Y-%m-%d_%H%M%S.log
When I ran pg_ctlcluster start, I only received "please chec
Wells Oliver writes:
> Alright but what's odd to me is that it's a standard out of the box ubuntu
> configuration, meaning:
>
> log_destination is 'stderr'
> logging_collector is on
> log_directory is /var/log/postgresql/
> log_filename is postgresql-%Y-%m-%d_%H%M%S.log
>
> When I ran pg_ctlclus
