Re: Parameter Settings - Instance-Database-Specific

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Edwin UY <edwin(dot)uy(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Parameter Settings - Instance-Database-Specific
Date: 2025-02-02 15:19:05
Message-ID: 351638.1738509545@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ron Johnson <ronljohnsonjr(at)gmail(dot)com> writes:
> On Sun, Feb 2, 2025 at 7:53 AM Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:
>> 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?

> 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.

More precisely, it shows you the values that prevail at this moment
in your own session. You can tell where those values came from
via the "source" column, but it won't tell you anything about
values that might've been locally overridden.

I think psql's "\drds" command might be what Edwin is looking for.

>> Is this true for both Aurora PostgreSQL / RDS and non-AWS PostgreSQL?

[ shrug... ] Most people on this list only know about community
Postgres. You'd have to ask AWS whether Aurora differs in this
area.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message di.liu 2025-02-03 01:45:47 RE: PostgreSQL Timeline Issue After Switchover with Pacemaker
Previous Message Ron Johnson 2025-02-02 14:57:06 Re: Parameter Settings - Instance-Database-Specific