| From: | Chris Angelico <rosuav(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: large database |
| Date: | 2012-12-11 11:36:15 |
| Message-ID: | CAPTjJmphyLRBQqFrc4buWJGJUKav=1UMc0UKTGLWbAtUXH=t-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 11, 2012 at 9:33 PM, Gavin Flower
<GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
>
> On Tue, Dec 11, 2012 at 7:26 AM, Mihai Popa <mihai(at)lattica(dot)com> wrote:
> > Second, where should I deploy it? The cloud or a dedicated box?
>
> Would you say the issue is cloudy?
> (I'm not being entirely facetious!)
*Groan* :)
It's certainly not clear-cut in the general case. In our specific
case, cloud was definitely not the way to go (we have other systems in
place for handling scale-out, so it's better for us to simply get X
dedicated computers and have an administrative decision to scale up to
Y, rather than automate it up and down as cloud can do).
ChrisA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zbigniew | 2012-12-11 11:36:31 | Re: Problem with aborting entire transactions on error |
| Previous Message | Zbigniew | 2012-12-11 11:28:33 | Re: Problem with aborting entire transactions on error |