Re: Optimization of vacuum for logical replication
| От | Kyotaro Horiguchi |
|---|---|
| Тема | Re: Optimization of vacuum for logical replication |
| Дата | |
| Msg-id | 20190822.121323.59215860.horikyota.ntt@gmail.com обсуждение |
| Ответ на | Re: Optimization of vacuum for logical replication (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>) |
| Ответы |
Re: Optimization of vacuum for logical replication
Re: Optimization of vacuum for logical replication |
| Список | pgsql-hackers |
Hello. At Wed, 21 Aug 2019 18:06:52 +0300, Konstantin Knizhnik <k.knizhnik@postgrespro.ru> wrote in <968fc591-51d3-fd74-8a55-40aa770baa3a@postgrespro.ru> > Ok, you convinced me that there are cases when people want to combine > logical replication with streaming replication without slot. > But is it acceptable to have GUC variable (disabled by default) which > allows to use this optimizations? The odds are quite high. Couldn't we introduce a new wal_level value instead? wal_level = logical_only I think this thread shows that logical replication no longer is a superset(?) of physical replication. I thougt that we might be able to change wal_level from scalar to bitmap but it breaks backward compatibility.. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: