sendob

8 ms·

31.
by sendob 14y ago
I don't think this is a very helpful or accurate statement. I would encourage people to actually investigate things for themselves. Generally you do trade some performance (depending upon implementation, they can be closer to the metal so
32.
by sendob 14y ago
http://mondrian.pentaho.com/ Is one I have used in the past
33.
by sendob 14y ago
I agree! Geography is very valuable to some individuals; Especially with the tools available at this point, it seems strange to value being physically co-located for work.
34.
by sendob 14y ago
I agree, I don't think this reflects well on the postgres community( in so far that Heroku is a member of that community ). Heroku has certainly done a lot to demonstrate how effective postgres can be practice, in addition to other contribu
35.
by sendob 14y ago
you are good to be suspicious into any benchmark(as even the original slides note). I dont think we really have any information as it relates to transaction boundaries present, nor clients used: From the slides: "Scripts read a CSV ﬁle, pa
36.
by sendob 14y ago
from the link: "In Postgres 9.2, this improvement automatically becomes available without any further configuration." "Essentially, it accomplishes this by reducing the lock contention surrounding an internal lock called WALWriteLock. When
37.
by sendob 14y ago
that post, also discusses using a 7200rpm disk. I think where you may be confused is considering them as distinct IO operations, vs seeing it as a point which must have been flushed past ( sequentially )
38.
by sendob 14y ago
http://pgeoghegan.blogspot.com/2012/06/towards-14000-write-t... may interest you