pgx failover support without database/sql

[clemensg]

Describe the feature

It seems this wrapper was designed to be used with database/sql only and not when using pgx directly, which is often required for advanced Postgres features. Any ideas/plans on how to leverage fast failover detection when using pgx/v5 without database/sql ?

Use Case

We often can't use database/sql. It is also more performant to use pgx directly instead of via database/sql.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

The AWS Advanced Go Wrapper version used

2025-07-31

Go version used

1.24

Operating System and version

Linux

[aaronchung-bitquill]

Hi @clemensg

Thank you for reaching out and showing interest in our wrapper driver.

That is correct. The AWS Advanced Go Wrapper does not currently support using pgx directly. While we cannot comment on timelines, support for using pgx direcrtly and its features are currently in the backlog.

If you don't mind, I was wondering if you would be willing to share a little more of your use case? Are there any particular Advanced PostgreSQL features or pgx features that you are using or have particular interest in?

Thank you!

[clemensg]

Hi @aaronchung-bitquill,

Good to hear that this is on the backlog.

Our use case involves various Go services interacting with Multi-AZ Aurora Postgres databases, where improved failover times could be very beneficial. The main advantages we see in using pgx directly are support for batching (via pgx.Batch) and LISTEN/NOTIFY (via WaitForNotification).

Thank you for considering this!

Best regards,
Clemens

[joschi]

Same here.

We're also using pgx5 throughout our codebase and migrating to database/sql would be a major undertaking and it's not possible to replace pgx5 in every single case.