| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(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 18:17:56 |
| Message-ID: | 20130409181756.GX4361@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
* Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
> And I think the increased exposure and thus increased likelihood of
> leakage due to more widespread usage holds some weight
This is most appropriately addressed on a case-by-case basis regarding
the specific situation. Such classification should be done by -core (or
some similar committee) and then we should have a policy which can be
followed based on that classification. My hope is that the very general
policy which I outlined could simply be tailored based on the
classification.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2013-04-09 18:22:44 | Re: Heroku early upgrade is raising serious questions |
| Previous Message | Stephen Frost | 2013-04-09 18:13:58 | Re: Heroku early upgrade is raising serious questions |