PgBouncer special settings?

[MrBadge]

When connecting to the DB through the PgBouncer the following errors approximately every 30 seconds are received:

pg: 2019/09/17 20:52:10 listener.go:126: pg: discarding bad listener connection: pg: readSimpleQuery: unexpected message 'A'

Seems it should be notificationResponseMsg, but the error comes from the readSimpleQuery method.

PG connection options:

opts := &pg.Options{
		User:        conf.User,
		Password:    conf.Pass,
		Database:    conf.DB,
		Addr:        fmt.Sprintf("%s:%s", conf.Host, conf.Port),
		PoolSize:    10,
		PoolTimeout: time.Second * 30,
	}

Do I have to use MaxConnAge or some other options to avoid this?

[MrBadge]

Found that PG listeners are incompatible with the Transaction pooling method of PgBouncer (https://pgbouncer.github.io/features.html)

[kidoman]

So what pooling method did you end up using? I need to use pgbouncer with go-pg so trying to make sure I am prepared.

[MrBadge]

@kidoman session pooling was the only option, because of the listen\notify support

[kidoman]

@MrBadge thanks for the reply. Does session pooling help with too many idle conenctions being held by individual containers with go-pg? I will do my own research of course, but thought you might already have encountered this issue.