Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6
| От | Greg Stark |
|---|---|
| Тема | Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 |
| Дата | |
| Msg-id | CAM-w4HN+0jnvN6cNitNFBuz9Au3E4KfVrPg4Uq+NwW+5LqoeeA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 (Josh Berkus <josh@agliodbs.com>) |
| Список | pgsql-hackers |
On Thu, Mar 13, 2014 at 5:10 PM, Josh Berkus <josh@agliodbs.com> wrote: > First, I'll note that one of the reasons we haven't had a bunch of > reports from the field about this is that a lot of our users have yet to > apply 9.3.3, so if they have corruption issues they probably attribute > them to the issues which are fixed in 9.3.3. I know that's the case > with our customer base. I was speculating that the reason we saw a sudden bunch after 9.3.3 might be that there might be a number of people who wait N releases before upgrading and the number of people for whom the value of N is 3 might be significant. Or it could be a coincidence. Users will only notice if they fail over to their standby or run queries on their standby. -- greg
В списке pgsql-hackers по дате отправления: