From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Selena Deckelmann <selena(at)chesnok(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: The case for version number inflation |
Date: | 2013-02-28 01:28:57 |
Message-ID: | 20130228012857.GN16142@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
* Selena Deckelmann (selena(at)chesnok(dot)com) wrote:
> On Wed, Feb 27, 2013 at 2:55 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > And you're probably aware of the issue with Amazon Linux, where they
> > don't distinguish between version 9.1 and 9.2 and thus corrupt people's
> > databases.
>
> This seems like a case to be made for Postgres to respond more elegantly to
> this situation, possibly by converting blocks on the fly to the newer
> version of the database for writes and being ok with reading previous
> versions of blocks, or simply not writing data to the filesystem when the
> versions don't match.
It'd certainly be wonderful, but we're simply not there yet. :) This
does not excuse poor packaging- that's what the packaging is supposed to
be there to address.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-02-28 01:30:31 | Re: The case for version number inflation |
Previous Message | Gavin Flower | 2013-02-28 01:19:17 | Re: The case for version number inflation |