| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(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 00:50:32 |
| Message-ID: | 516365D8.9090600@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
> 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.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-04-09 01:20:18 | Re: Heroku early upgrade is raising serious questions |
| Previous Message | Adrian Klaver | 2013-04-09 00:13:47 | Re: Heroku early upgrade is raising serious questions |