PGBouncer is a lightweight connections pooler for PostgreSQL. There are instances where PGBouncer can be used with CockroachDB to offset the high costs of having many active connections, segregation of responsibilities (i.e. business analysts are segregated from the mission-critical users) serverless applications needing pooling mechanisms. PGBouncer comes standard with various types of authentication mechanisms, and we're going to explore a few compatible with CockroachDB. We already explored trust and cert in my previous article, feel free to review that if you need a refresher.
Previous Articles
- Using PGBouncer with CockroachDB
- Using PGBouncer with Cockroach Cloud Free Tier
- Exploring PGBouncer auth_type(s) with CockroachDB
Motivation
CockroachDB offers a rich gamut of authentication mechanisms. The most widely accepted by engineering is cert-based authentication. We also support gss, but within the context of PGBouncer, it is not supported. For today's session, I will cover the remaining supported types in PGBouncer and how they translate to CockroachDB. For a brief overview of all available PG and CockroachDB auth methods, I'd like to direct you to an in-depth blog by one of our engineers. Also, I must mention that everything stated in this article may be dated by the time you read this as CockroachDB is under active development and we may support more auth_type(s) later.
from DZone.com Feed https://ift.tt/3DGWUIC
No comments:
Post a Comment