| From: | zaidagilist <zaidagilist(at)gmail(dot)com> |
|---|---|
| To: | Siraj G <tosiraj(dot)g(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Is PgAudit extension database specific? |
| Date: | 2026-01-06 17:29:39 |
| Message-ID: | CAFS1Kf4ZH0XAcU3H1FCFgy65=tTc+-wnDq=-XunseW30V4KBHw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dharin Shah | 2026-01-06 17:55:07 | Re: Is PgAudit extension database specific? |
| Previous Message | David G. Johnston | 2026-01-06 17:26:59 | Re: Is PgAudit extension database specific? |