From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Postgres upgrade, security release, where? |
Date: | 2013-04-02 08:34:39 |
Message-ID: | CA+OCxoy8GVPUpUZr5zDP+z2gFR4aoUbE_+uD=+xNLc9gXm27TA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Apr 1, 2013 at 11:43 PM, Mark Kirkwood
<mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
> On 02/04/13 13:55, Bruce Momjian wrote:
>>
>> On Tue, Apr 2, 2013 at 09:40:07AM +0900, Ian Lawrence Barwick wrote:
>>>>
>>>> Due to the security nature of the release, the source and binaries will
>>>> only be publicly available on April 4 --- there are no pre-release
>>>> versions available.
>>>
>>>
>>> The PostgreSQL homepage has a big announcement saying
>>> "PostgreSQL minor versions released!", including a mention of a
>>> "security issue";
>>> unfortunately it's not obvious that this is for the prior 9.2.3 release
>>> and as
>>> the announcement of the upcoming security release
>>> ( http://www.postgresql.org/about/news/1454/ ) does not mention the
>>> new release number, methinks there is plenty of room for confusion :(
>>>
>>> It might be an idea to update the "splash box" with details of the
>>> upcoming
>>> release.
>>
>>
>> I agree updating the "spash box" would make sense.
>>
>
> Or perhaps include a date on said splashes, so we know when to panic :-)
I've added the date to the splash. You can cease panicing now :-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2013-04-02 08:47:21 | Re: Postgres upgrade, security release, where? |
Previous Message | Armand du Plessis | 2013-04-02 08:16:57 | Re: Problems with pg_locks explosion |