Re: Transaction-controlled robustness for replication
| От | Marko Kreen |
|---|---|
| Тема | Re: Transaction-controlled robustness for replication |
| Дата | |
| Msg-id | e51f66da0807221539v2bbb75ej3b17356101510364@mail.gmail.com обсуждение исходный текст |
| Ответ на | Transaction-controlled robustness for replication (Simon Riggs <simon@2ndquadrant.com>) |
| Ответы |
Re: Transaction-controlled robustness for replication
|
| Список | pgsql-hackers |
On 7/22/08, Simon Riggs <simon@2ndquadrant.com> wrote: > We could represent this with 3 parameters: > synchronous_commit = on | off > synchronous_standby_transfer = on | off > synchronous_standby_wal_fsync = on | off > > If we are able to define these robustness characteristics for each > transaction *separately* then it will represent an industry first: no > other database has that capability implemented or planned on published > roadmaps, nor has it been discussed in research to my knowledge. > > Changing the parameter setting at transaction-level would be expensive > if we had to set three parameters. How about extending BEGIN.with additional keywords? -- marko
В списке pgsql-hackers по дате отправления: