Re: switch UNLOGGED to LOGGED
| От | Robert Haas |
|---|---|
| Тема | Re: switch UNLOGGED to LOGGED |
| Дата | |
| Msg-id | BANLkTi=d+M8bxzxq0UNa+Cr_mO4uD4DigQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: switch UNLOGGED to LOGGED (Noah Misch <noah@leadboat.com>) |
| Ответы |
Re: switch UNLOGGED to LOGGED
Re: switch UNLOGGED to LOGGED |
| Список | pgsql-hackers |
On Fri, May 27, 2011 at 6:19 AM, Noah Misch <noah@leadboat.com> wrote: >> So, it's ok to have a log item that is replayed only if >> >> WalRcvInProgress() >> >> is true? > > No, that checks for WAL streaming in particular. A log-shipping standby needs > the same treatment. > >> Is it a correct approach? I couldn't find any other way to >> find out if we are in a standby or a master... > > InArchiveRecovery looks like the right thing, but it's currently static to > xlog.c. Perhaps exporting that is the way to go. Why is it necessary to replay the operation only on the slave? Can we just use XLOG_HEAP_NEWPAGE? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: