PostgreSQL Manager: roles, access and routine DBA work

PostgreSQL Manager handles PostgreSQL users, roles and permissions, failed logins, exhausted connections, blocking sessions and bloat, within the access you give it.

REQUEST DEMO

READ THE DOCS

2501's PostgreSQL Manager specialty works PostgreSQL tickets end to end: users and roles, permissions, connection and login problems, and routine maintenance. It investigates before it changes anything, and the riskiest changes wait for a person.

A new service account can read last month's tables but not yesterday's. An application runs out of connections at its busiest hour, or a session left open mid-transaction holds a lock that everything else queues behind. None of it is difficult, but each ticket waits for a DBA and has to be exactly right.

What 2501 does

The PostgreSQL specialty takes these requests from your ticketing system and works on clusters running on Unix and Linux servers. It creates, renames and removes users and roles, rotates passwords, and grants or revokes access to schemas and tables, including tables created later. It troubleshoots unreachable servers, exhausted connections, failed logins, long-running queries and blocking sessions, and looks after maintenance and storage: bloated tables and indexes, upkeep that has fallen behind, growing transaction logs and oversized databases. What it changed, and why, is always reported.

Scope map of 2501's PostgreSQL Manager: it manages users, roles, passwords and access, troubleshoots connections and queries, and looks after maintenance and storage; elevated privileges, configuration changes, restarts, failover, restores and dropping a database need approval, and application data is never modified.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Risky changes need approval: granting elevated privileges, configuration changes, restarts, failover, restores and dropping a database.
Access and rules set the limits: the agent holds only the access you grant, your rules decide which clusters are in scope, and destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Will it change application data to make a query work? No. It does not modify application data or bypass the rules on who may see which rows to get a query through.

What if the real problem is a full disk? It hands the ticket to the specialty for that, with its findings: the disk specialty, for example, when transaction logs have filled the disk.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

PostgreSQL out of connections gets room back after 2501 finds what is holding them, clears the sessions that are clearly stuck and names the application behind the problem, leaving the connection limit to a person

Problem

PostgreSQL running out of connections

Raising the connection limit hides whatever is holding PostgreSQL connections. How 2501 finds it, frees stuck sessions gently and leaves configuration and restarts to you.

See how it is handled

PostgreSQL Manager: roles, access and routine DBA work

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE