Re: scaling postgres

From: Seref Arikan <serefarikan(at)kurumsalteknoloji(dot)com>
To: Chris Withers <chris(at)simplistix(dot)co(dot)uk>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: scaling postgres
Date: 2015-08-04 08:11:51
Message-ID: CA+4ThdrM-A5_DLmRgxJRo036RyL_=fn6wzGmkC9=FRaHQODjPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 4, 2015 at 9:06 AM, Chris Withers <chris(at)simplistix(dot)co(dot)uk>
wrote:

> On 03/08/2015 08:34, Seref Arikan wrote:
>
>>
>>
>> At what point does postgres stop scaling?
>> What happens when the computational load no longer fits on one
>> machine? What are the options then?
>>
>>
>> I think it is hard to come up with blanket responses to generic
>> questions such as "What happens when the computational load no longer
>> fits on one machine?"
>>
>
> Of course, I guess I'm looking out for the pain points that people
> commonly hit with chunky postgres installs...
>
> I work in healthcare and patient centric records let me consider
>> multiple servers for lots and lots of patients. The engineering team
>> from instagram has been sharing their experience with postgres, which is
>> possible due to their domain model.
>>
>
> I'll have a google, but do you have the Instagram links you're thinking of?
>
>
> Nope, sorry, Google is your friend :)

> cheers,
>
> Chris
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Withers 2015-08-04 08:38:38 Re: scaling postgres
Previous Message Chris Withers 2015-08-04 08:06:41 Re: scaling postgres