PG Bug reporting form <noreply@postgresql.org> writes:
> We are connecting to a Postgres-XL server from a SQL Server Integration
> Services (SSIS, from now) using an OLEDB driver solution developed by
> Intellisoft. The PostgresXL server is deployed in a Centos 7 machine with a
> PGBouncer pool.
> Monthly, we are facing an issue that consists in connection failures between
> SSIS and PGBouncer. The pooler is showing the following error:
> ssl3_get_client_certificate:peer did not return a certificate
> PGBouncer is rejecting the connection, so PostgresXL server is never
> reached. In order to resolve this issue, we have to reinstall the PostgresXL
> certificates in the Windows Server. After that, the connection can be
> reestablished without any server interventions.
Weird ... but I'm afraid you have come to the wrong place for help.
This mailing list deals with PG server bugs, and the server seems to
be the one component that is clearly not at fault in your case.
It could be PGBouncer's fault, so I'd suggest inquiring through their
support contact. (I do not know offhand what that is, but it's not
here.) But TBH, if reinstalling the identical certificates on the
client machine makes the problem go away, it's hard to conclude that
it's not a client-side bug.
regards, tom lane