| From: | Chris Withers <chris(at)simplistix(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: scaling postgres |
| Date: | 2015-08-04 08:06:41 |
| Message-ID: | 55C07291.3050502@simplistix.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
cheers,
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seref Arikan | 2015-08-04 08:11:51 | Re: scaling postgres |
| Previous Message | Chris Withers | 2015-08-04 08:04:33 | Re: scaling postgres - can child tables be in a different tablespace? |