| From: | Dharin Shah <dharinshah95(at)gmail(dot)com> |
|---|---|
| To: | zaidagilist <zaidagilist(at)gmail(dot)com> |
| Cc: | Siraj G <tosiraj(dot)g(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Is PgAudit extension database specific? |
| Date: | 2026-01-06 17:55:07 |
| Message-ID: | CAOj6k6f53Yag0trVUUHq5vrzREVFkicDpiG2WNjpivHMYANzKg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello,
This is standard for all pg extensions as mentioned above.
Just adding a minor doc patch to add clarification in the doc.
Thanks,
Dharin
On Tue, Jan 6, 2026 at 6:30 PM zaidagilist <zaidagilist(at)gmail(dot)com> wrote:
> Hello Siraj,
>
> pgAudit is a coupled component build for a specific PG version, for each
> PG version you are required to install separately. Same behavior as other
> PG based extensions.
>
> Regards,
> Zaid
>
> On Tue, Jan 6, 2026 at 10:19 PM Siraj G <tosiraj(dot)g(at)gmail(dot)com> wrote:
>
>> Hello Experts!
>>
>> Here is my observation:
>>
>> Connected to postgres DB and ran:
>> CREATE EXTENSION pgaudit;
>>
>> Within postgres DB, I ran this:
>> SELECT * FROM pg_catalog.pg_extension WHERE extname = 'pgaudit';
>>
>> It does return a row.
>>
>> I changed the DB and ran the same SQL, but it does not return any thing.
>>
>> The PostgreSQL instance is a GCP cloud SQL running with postgres V14.19.
>>
>> Would you help me understand this, please.
>>
>> Regards
>> Siraj
>>
>>
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-doc-clarify-pg_extension-is-per-database-not-cluster.patch | application/octet-stream | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-01-09 15:50:28 | Better way to monitor for failed replication? |
| Previous Message | zaidagilist | 2026-01-06 17:29:39 | Re: Is PgAudit extension database specific? |