Skip site navigation (1) Skip section navigation (2)

pgbouncer + psql 9.0a4

From: Garick Hamlin <ghamlin(at)isc(dot)upenn(dot)edu>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: pgbouncer + psql 9.0a4
Date: 2010-02-26 16:26:23
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
I was just trying out 9.0a4 and I noticed.  That I can't connect to 
pgbouncer with psql from 9.0a4 as a result of the set application_name 
changes to psql.

I imagine this is really mostly pgbouncer's problem, but I couldn't 
figure out how if it was possible to make psql not set application_name 
from the psql man page.  If not, at least from a users point of view psql 
9.0a4 looks incompatible with existing versions of pgbouncer in at least 
in this configuration that works with an older versions of psql.

... or, is that a crazy way to look at it?


Details are below..

My setup (Solaris 10 / sparc )

[ psql 9.0a4 ] -> [ pgbouncer 1.3.1 ] -> [ postgres 9.0a4 ]

$ /usr/local/var/postgres/9.0a4/bin/psql -h -p 6543
psql: ERROR:  Unknown startup parameter

..pgbouncer's log..
2010-02-25 21:56:29.721 6979 WARNING C-71d48: (nodb)/(nouser)@ unsupported startup parameter: application_name=psql
2010-02-25 21:56:29.721 6979 LOG C-71d48: (nodb)/(nouser)@ closing because: Unknown startup parameter (age=0)
2010-02-25 21:56:29.722 6979 LOG C-71d48: (nodb)/(nouser)@ Pooler Error: Unknown startup parameter

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-26 16:27:11
Subject: Re: Avoiding bad prepared-statement plans.
Previous:From: Tom LaneDate: 2010-02-26 16:14:01
Subject: Re: NaN/Inf fix for ECPG

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group