From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Komal Habura <komalhabura2(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Seek for helper documents to implement WAL with an FDW |
Date: | 2023-02-22 13:35:34 |
Message-ID: | 37369af8-0b66-94ba-38f5-dccadfa2e1d3@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20.02.23 10:53, Komal Habura wrote:
> I have written an FDW, which is similar to the file_fdw. I need
> the support of WAL to perform logical and stream replication. I have
> knowledge about custom WAL but do not have clarity about implementing
> WAL(writing, redo, desc, identify, etc..) and cases where WAL can be
> applied.
A foreign-data wrapper manages *foreign* data, which almost by
definition means that it does not participate in the transaction
management of the local PostgreSQL instance, including in the WAL. If
you want to build a custom storage format that does participate in the
local transaction management, you should probably look at building
either a table access method or a storage manager.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2023-02-22 13:39:23 | Re: Raising the SCRAM iteration count |
Previous Message | Peter Eisentraut | 2023-02-22 13:23:51 | Re: Improving inferred query column names |