| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Pradeep Kumar <spradeepkumar29(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, "bharath(dot)rupireddyforpostgres(at)gmail(dot)com" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com> |
| Subject: | Re: Extensible Rmgr for Table Ams |
| Date: | 2023-02-14 17:31:09 |
| Message-ID: | 1f7ce8804f95159159c7df65b83cddc6debb1819.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2023-02-14 at 19:09 +0530, Pradeep Kumar wrote:
> GetRmgrDesc() are widely used in XLogDumpDisplayRecord() and
> XLogDumpDisplayStats() in pg_waldump.c. In function GetRmgrDesc() for
> custom resource managers by the default they are assign
> 1) rm_desc = default_desc
> 2) rm_identify = default_identify
> Suggest some ways to register my own rm_desc and rm_identify in
> RmgrDescTable[]?
The binaries like pg_waldump, etc., don't load server extensions. It
makes sense to allow utilities to also parse custom WAL records
somehow, but right now I don't have a concrete proposal.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-02-14 17:47:55 | Re: Weird failure with latches in curculio on v15 |
| Previous Message | Laurenz Albe | 2023-02-14 16:53:33 | Re: Allow tailoring of ICU locales with custom rules |