| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
| Date: | 2026-02-18 03:26:53 |
| Message-ID: | aZUxffYZuZB9gHWz@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 15, 2026 at 02:38:40PM -0500, Andres Freund wrote:
> And again, any users with more than the bare minimum of permissions can cause
> arbitrarily much WAL to be emitted, in very hard to identify ways. If you're
> concerned about users triggering too high WAL usage, ISTM your time would be
> much better spent introducing infrastructure to track per-session or even per
> user WAL generation.
For the per-session tracking, this is what the backend-level
statistics are basically able to do for WAL data since v18, no? For
user-level tracking, I don't think that it would be that difficult to
implement, I am just not sure how relevant it could be for real world
cases.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | VASUKI M | 2026-02-18 04:19:47 | Re: BUG #19095: Test if function exit() is used fail when linked static |
| Previous Message | Michael Paquier | 2026-02-18 02:34:19 | Re: Our ABI diff infrastructure ignores enum SysCacheIdentifier |