| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | "satyanarlapuram(at)gmail(dot)com" <satyanarlapuram(at)gmail(dot)com>, "marvin_liang(at)qq(dot)com" <marvin_liang(at)qq(dot)com>, "actyzhang(at)outlook(dot)com" <actyzhang(at)outlook(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Subject: | Re: pg_walinspect - a new extension to get raw WAL data and WAL stats |
| Date: | 2021-09-09 22:49:46 |
| Message-ID: | A0BDA184-3564-4FC0-8B71-B16B5D828B9F@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/8/21, 6:49 AM, "Bharath Rupireddy" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> How about we create a new extension, called pg_walinspect (synonymous
> to pageinspect extension) with a bunch of SQL-callable functions that
> get the raw WAL records or stats out of a running postgres database
> instance in a more structured way that is easily consumable by all the
> users or DBAs or developers? We can also provide these functionalities
> into the core postgres (in xlogfuncs.c) instead of a new extension,
> but we would like it to be pluggable so that the functions will be
> used only if required.
+1
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-09 22:54:54 | Re: We don't enforce NO SCROLL cursor restrictions |
| Previous Message | Bossart, Nathan | 2021-09-09 22:30:54 | Re: parallelizing the archiver |