Hi On Mon, Jan 11, 2021 9:14 AM Tsunakawa, Takayuki <tsunakawa.ta...@fujitsu.com> wrote: > From: Masahiko Sawada <sawada.m...@gmail.com> > > I think it's better to have index AM (and perhaps table AM) control it > > instead of filtering in XLogInsert(). Because otherwise third-party > > access methods that use LSN like gist indexes cannot write WAL records > > at all when wal_level = none even if they want. > > Hm, third-party extensions use RM_GENERIC_ID, so it should probably be > allowed in XLogInsert() as well instead of allowing control in some other way. > It's not unnatural that WAL records for in-core AMs are filtered in > XLogInsert(). I updated the patch following this discussion, and fixed the documentation as well. No failure is found during make check-world.
Best Regards,
Takamichi Osumi
disable_WAL_logging_v06.patch
Description: disable_WAL_logging_v06.patch
