PostgreSQL /etc/postgresql/11/main/pg_ident.conf

Original 📋 Debian 10 (Buster) 42 lines

Works On

Viewing:
Debian 10 (Buster)
Same on:
Other versions:

Details

Size
42 lines
MD5
f11c8332d3f444148c0b8ee83ec5fc6d
SHA256
297f466913f31ff2dcfceea5ccb1a03027db54d9a95270dfd8044cb0c5b016a8
/etc/postgresql/11/main/pg_ident.conf
# PostgreSQL User Name Maps
# =========================
#
# Refer to the PostgreSQL documentation, chapter "Client
# Authentication" for a complete description.  A short synopsis
# follows.
#
# This file controls PostgreSQL user name mapping.  It maps external
# user names to their corresponding PostgreSQL user names.  Records
# are of the form:
#
# MAPNAME  SYSTEM-USERNAME  PG-USERNAME
#
# (The uppercase quantities must be replaced by actual values.)
#
# MAPNAME is the (otherwise freely chosen) map name that was used in
# pg_hba.conf.  SYSTEM-USERNAME is the detected user name of the
# client.  PG-USERNAME is the requested PostgreSQL user name.  The
# existence of a record specifies that SYSTEM-USERNAME may connect as
# PG-USERNAME.
#
# If SYSTEM-USERNAME starts with a slash (/), it will be treated as a
# regular expression.  Optionally this can contain a capture (a
# parenthesized subexpression).  The substring matching the capture
# will be substituted for \1 (backslash-one) if present in
# PG-USERNAME.
#
# Multiple maps may be specified in this file and used by pg_hba.conf.
#
# No map names are defined in the default configuration.  If all
# system user names and PostgreSQL user names are the same, you don't
# need anything in this file.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------

# MAPNAME       SYSTEM-USERNAME         PG-USERNAME

Copy & Paste

curl:
curl https://exampleconfig.com/api/v1/config/original/f11c8332d3f444148c0b8ee83ec5fc6d?hint=pg_ident.conf
wget:
wget -O pg_ident.conf https://exampleconfig.com/api/v1/config/original/f11c8332d3f444148c0b8ee83ec5fc6d?hint=pg_ident.conf

For AI Agents

<prompt><role>DevOps agent</role><source url='https://exampleconfig.com/api/v1/config/original/f11c8332d3f444148c0b8ee83ec5fc6d?hint=pg_ident.conf' /><config><app>PostgreSQL</app><os>Debian 10 (Buster)</os><location>/etc/postgresql/11/main/pg_ident.conf</location><lines>42</lines><md5>f11c8332d3f444148c0b8ee83ec5fc6d</md5><sha256>297f466913f31ff2dcfceea5ccb1a03027db54d9a95270dfd8044cb0c5b016a8</sha256></config></prompt>

Paste into Claude, ChatGPT, or any AI assistant.

Install PostgreSQL

Alpine Linux

sudo apk add postgresql

Debian

sudo apt update && sudo apt install postgresql

Red Hat Enterprise Linux

sudo yum install postgresql17-server

Ubuntu

sudo apt update && sudo apt install postgresql

File Location

File Path
/etc/postgresql/11/main/pg_ident.conf
Directory
/etc/postgresql/11/main/
Significance
System-wide configuration directory
Description
Files in /etc/ contain system-wide configuration settings that affect all users.

FAQ

When should I use this pg_ident.conf?

Use it to restore a missing default, confirm what shipped, or diff against your current PostgreSQL config.

How do I restore PostgreSQL defaults?

Download the file, back up the current one in /etc/postgresql/11/main/pg_ident.conf, replace it, then reload or restart PostgreSQL.

Is pg_ident.conf safe for production?

It is the vendor default for Debian 10 (Buster). Treat it as a baseline and review security and performance settings before production use.

How does this differ from other OS versions?

Defaults vary by distro and version. This copy matches Debian 10 (Buster).

Can I use this for PostgreSQL troubleshooting?

Yes. Diff it against yours to find drift, then restore only the sections you need.