mark <dvlhntr(at)gmail(dot)com> writes:
> client connection runs through bouncer (session pooling) to a 9.2.4
> postgres back end. I have had this problem happen without bouncer in the
> middle but for this limited debug bouncer is in play. have numerous clinets
> copying to the same table throughout the day, often concurrently.
I wonder whether pgbouncer realizes that it should force-disconnect its
database connection if the client disconnects ungracefully. Your
backend is evidently waiting for COPY data that won't be forthcoming;
the only way to get it out of that is to drop the connection.
regards, tom lane