| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jethish Jethish <jethish777(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL Log Info |
| Date: | 2024-11-22 16:15:22 |
| Message-ID: | CAKFQuwYWegiCQeQWtEM6unoAis_R=1JKWxehwJM51LFXegreqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Nov 22, 2024 at 12:32 AM Jethish Jethish <jethish777(at)gmail(dot)com>
wrote:
> If an select query is fired I need the query returned values needs to be
> logged in my PostgreSQL log file.
>
Then the answer is no, and unlikely to become a feature anyone would
develop or that we'd accept.
A more innovative solution is going to need to be thought up to
satisfy the security people that want to know what data was acquired from
their system by either their users or semi-privileged hackers (privileged
exploits would likely just disable such logging anyway). The space of
setting up a proxy server in between clients and the PostgreSQL server is
under-explored as a means by which to incorporate such functionality
externally to the core server.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jethish Jethish | 2024-11-22 16:26:30 | Re: PostgreSQL Log Info |
| Previous Message | Adrian Klaver | 2024-11-22 16:02:54 | Re: PostgreSQL Log Info |