Re: scaling postgres

On 03/08/2015 08:15, Jony Cohen wrote:
> SSD disks are cheep these days but they don't like repeated
> writes/deletes so it might cause problems down the line (hence my
> first RAM recommendation)
>
> as for keeping the raw data - you could easily do it if you use
> partitions, if you have daily partitions inheriting from a master
> table you can quickly access the last day (or even several days)
> but do take note that a full table scan takes time and you'll need to
> manage writing to the right partition yourself (not that hard - simply
> insert to <tablename>_<date>)
>
> if you can write the data daily, keeping it will not add any real load
> (a little on parse times for queries that access the master table)

Interesting, you seem a lot less fussed by these numbers than I am,
which is good to hear!

At what point does postgres stop scaling?
What happens when the computational load no longer fits on one machine?
What are the options then?

cheers,

Chris