Dave Page <dpage@postgresql.org> writes:
> I'm not going to comment on who's fault it is, but the OP quoted 100
> updates and 600 selects per *second*. I can't imagine Flickr or Slashdot
> (which is heavily csched for reading) are under anything like that sort
> of constant load.
I'm pretty sure I remember reading that Slashdot had to put enormous
amounts of cacheing in front of their DB to keep it from falling over
on a regular basis.
regards, tom lane
