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

Authentic ๐Ÿ“‹ Ubuntu 24.04 LTS (Noble Numbat) 73 lines

Compatibility

Currently viewing:
Ubuntu 24.04 LTS (Noble Numbat)
Also compatible:
Debian 11 (Bullseye) Debian 12 (Bookworm) Ubuntu 20.04 LTS (Focal Fossa) Ubuntu 22.04 LTS (Jammy Jellyfish)
Different versions:

File Info

Size
73 lines
MD5
a851d3eebbf853c646a25d241dd16767
SHA256
b4dfef08731a7d20a3bb724ad4cf3e1cd91ec01fbe51349c6a3acc5704072965

Quick Commands

curl:
curl https://exampleconfig.com/api/v1/config/original/a851d3eebbf853c646a25d241dd16767?hint=pg_ident.conf
wget:
wget -O pg_ident.conf https://exampleconfig.com/api/v1/config/original/a851d3eebbf853c646a25d241dd16767?hint=pg_ident.conf
/etc/postgresql/17/main/pg_ident.conf
# PostgreSQL User Name Maps
# =========================
#
# ---------------
# Mapping Records
# ---------------
#
# 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.
#
# PG-USERNAME can be "all", a user name, a group name prefixed with "+", or
# a regular expression (if it starts with a slash (/)).  If it is a regular
# expression, the substring matching with \1 has no effect.
#
# 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.
#
# ---------------
# Include Records
# ---------------
#
# This file allows the inclusion of external files or directories holding
# more records, using the following keywords:
#
# include           FILE
# include_if_exists FILE
# include_dir       DIRECTORY
#
# FILE is the file name to include, and DIR is the directory name containing
# the file(s) to include.  Any file in a directory will be loaded if suffixed
# with ".conf".  The files of a directory are ordered by name.
# include_if_exists ignores missing files.  FILE and DIRECTORY can be
# specified as a relative or an absolute path, and can be double-quoted if
# they contain spaces.
#
# -------------------------------
# Miscellaneous
# -------------------------------
#
# 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

How to 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

Configuration File Location

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

Complete PostgreSQL Configuration Guide

What is pg_ident.conf?
Access the original 'pg_ident.conf' (postgresql.conf) configuration file from a fresh PostgreSQL installation on Ubuntu 24.04 LTS (Noble Numbat). This is the exact default configuration that ships with the official PostgreSQL package, essential for database recovery, performance optimization, and understanding enterprise-grade settings.
Technical Details
Located at '/etc/postgresql/17/main/pg_ident.conf', this 73-line file controls shared buffers, WAL settings, autovacuum parameters, connection pooling, and query optimization. Powers some of the world's largest databases including Instagram, Spotify, and financial institutions processing millions of transactions daily.
Common Configuration Question
How do you configure PostgreSQL for optimal performance, high availability, and ACID compliance on Ubuntu 24.04?
Why Use This Configuration?
This factory-default configuration includes advanced indexing, full-text search capabilities, and enterprise security features. Critical for database administrators, data engineers, and developers building scalable applications with complex queries.

Frequently Asked Questions

When should I use this pg_ident.conf file?

Use this original configuration file when you need to restore PostgreSQL to its default state after misconfiguration, during fresh installations, or as a baseline for customization. It's particularly useful for troubleshooting when your current config isn't working properly.

How do I restore PostgreSQL to default settings?

Download this file and replace your current configuration at /etc/postgresql/17/main/pg_ident.conf. Make sure to backup your existing configuration first, then restart the PostgreSQL service to apply the changes.

Is this pg_ident.conf file secure for production use?

This is the factory-default configuration that ships with PostgreSQL on Ubuntu 24.04 LTS (Noble Numbat). While it provides a secure baseline, you should review and customize security settings based on your specific production requirements and compliance needs.

What's the difference between this and other OS versions?

This configuration is specifically from Ubuntu 24.04 LTS (Noble Numbat). Different operating systems and versions may have slightly different default settings, security patches, or feature availability. Check the compatibility section above for other OS versions.

Can I use this configuration file for PostgreSQL troubleshooting?

Yes, this original configuration is excellent for troubleshooting. Compare it with your current settings to identify modifications that might be causing issues, or temporarily replace your config with this one to isolate problems.