| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, damien clochard <damien(at)dalibo(dot)info>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Heroku early upgrade is raising serious questions |
| Date: | 2013-04-09 02:16:09 |
| Message-ID: | 516379E9.7010306@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 04/08/2013 05:50 PM, Josh Berkus wrote:
>
>> Agreed. As far as I can see things where handled in the Postgres way,
>> when in doubt err on the side of caution. I applaud the efforts of those
>> concerned and trust in their ability to build on the experience.
>
> Mostly I'd rather be arguing as to whether or not we should have given
> Heroku early deployment vs. arguing whether or not we could have
> prevented them from being hacked. The same goes for other users, which
> is why we're discussing policy now.
I am going to admit to being dense, but is it not the same thing?
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2013-04-09 03:35:04 | Re: Heroku early upgrade is raising serious questions |
| Previous Message | Joshua D. Drake | 2013-04-09 01:20:18 | Re: Heroku early upgrade is raising serious questions |