Re: Parameter Settings - Instance-Database-Specific

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Parameter Settings - Instance-Database-Specific
Date: 2025-02-02 14:57:06
Message-ID: CANzqJaCP0C63feoHBG-jCG_=MWrzhs6jNykANf_KrUHTtbuw+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Sun, Feb 2, 2025 at 7:53 AM Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:

> Hi,
>
> I have PostgreSQL Instance that has several DBs.
> I assume there are instance specific and database specific parameter
> settings?
> How do I check this? Using the source column of pg_setting?
> Is this true for both Aurora PostgreSQL / RDS and non-AWS PostgreSQL?
>
> => \d pg_settings
> View "pg_catalog.pg_settings"
> Column | Type | Collation | Nullable | Default
> -----------------+---------+-----------+----------+---------
> name | text | | |
> setting | text | | |
>
[snip]

>
> select distinct source from pg_settings ;
> source
> --------------------
> client
> configuration file
> default
> database
> override
> command line
> (6 rows)
>

What do you get when you run:
SELECT * FROM pg_setting WHERE source = ''database';

More important, though, is the fact that pg_settings does not have a
"datname" column. Thus, it's values are all global to the instance.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2025-02-02 15:19:05 Re: Parameter Settings - Instance-Database-Specific
Previous Message Edwin UY 2025-02-02 12:52:21 Parameter Settings - Instance-Database-Specific