Re: unite recovery.conf and postgresql.conf
| От | Josh Berkus |
|---|---|
| Тема | Re: unite recovery.conf and postgresql.conf |
| Дата | |
| Msg-id | 4ED939CD.4030109@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: unite recovery.conf and postgresql.conf (Josh Berkus <josh@agliodbs.com>) |
| Ответы |
Re: unite recovery.conf and postgresql.conf
|
| Список | pgsql-hackers |
All: *ping* Trying to restart this discussion, since the feature bogged down on spec. We have consensus that we need to change how replication mode is mangaged; surely we can reach consensus on how to change it? On 11/8/11 11:39 AM, Josh Berkus wrote: > >> configuration data somewhere else, but we really need to be able to tell >> the difference between "starting PITR", "continuing PITR after a >> mid-recovery crash", and "finished PITR, up and running normally". >> A GUC is not a good way to do that. > > Does a GUC make sense to you for how to handle standby/master for > replication? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-hackers по дате отправления: