Connection pools through DigitalOcean managed database cluster or through node-postgres on Next.js web application

Prior to setting up my DigitalOcean managed database cluster I was just using a local PostgreSQL database. I was using the node-postgres (https://node-postgres.com/) package to create a connection pool. I would create one connection pool instance and import that instance into my serverless functions to query the database. However, with the DigitalOcean managed database cluster it is recommended to use the built-in connection pool tool (which uses PgBouncer according to documentation). My question is if I use the DigitalOcean connection pool should I not use a connection pool through node-postgres? Currently I have a connection pool set up through node-postgres in my Next.js web application and a connection pool set up through DigitalOcean. I am not sure if this “double pooling” is bad practice or will cause issues. Thanks and let me know if I need to provide more info.