RE: Disable WAL logging to speed up data loading
| От | tsunakawa.takay@fujitsu.com |
|---|---|
| Тема | RE: Disable WAL logging to speed up data loading |
| Дата | |
| Msg-id | TYAPR01MB2990A36E60D64D3E11F928A9FEAB0@TYAPR01MB2990.jpnprd01.prod.outlook.com обсуждение исходный текст |
| Ответ на | Re: Disable WAL logging to speed up data loading (Masahiko Sawada <sawada.mshk@gmail.com>) |
| Ответы |
RE: Disable WAL logging to speed up data loading
|
| Список | pgsql-hackers |
From: Masahiko Sawada <sawada.mshk@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 allowingcontrol in some other way. It's not unnatural that WAL records for in-core AMs are filtered in XLogInsert(). Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: