Re: Reporting the commit LSN at commit time
| От | Michael Paquier |
|---|---|
| Тема | Re: Reporting the commit LSN at commit time |
| Дата | |
| Msg-id | CAB7nPqQRQ7QdTHi2afsVBwzGcnNUkHLXQXsktW+OQYoCYfsMWg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Reporting the commit LSN at commit time (Fujii Masao <masao.fujii@gmail.com>) |
| Список | pgsql-hackers |
On Fri, Aug 8, 2014 at 11:58 AM, Fujii Masao <masao.fujii@gmail.com> wrote: > On Fri, Aug 8, 2014 at 9:50 AM, Craig Ringer <craig@2ndquadrant.com> wrote: > ISTM that the proper solution to that problem is the introduction of > new synchronous replication mode which makes the transaction wait for > its WAL to be replayed by the standby. If this mode is used, a client > doesn't need to track the LSN of each transaction and check whether > the committed transaction has already replayed by the standby or not. Don't you need to combine that with the possibility to wait for N targets instead of 1 in synchronous_standby_names? You may want to be sure that the commit is done on a series of standbys before considering any further operations after this transaction commit. -- Michael
В списке pgsql-hackers по дате отправления: