| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Jozef Mlich <jmlich(at)redhat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 |
| Date: | 2014-03-13 17:23:29 |
| Message-ID: | CAM-w4HN+0jnvN6cNitNFBuz9Au3E4KfVrPg4Uq+NwW+5LqoeeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 13, 2014 at 5:10 PM, Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-03-13 17:24:44 | Re: JSON Patch (RFC 6902) support? |
| Previous Message | Josh Berkus | 2014-03-13 17:10:00 | Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 |