Greetings all,
I'm trying to wrap my head around updating my configuration files, which
have been probably fairly static since before 8.4.
I've got some beefy hardware but have some tables that are over 57GB raw
and end up at 140GB size after indexes are applied. One index creation took
7 hours t
Hi Jason, oddly enough the setting on or off does not affect this particular
issue. As a rule I generally enable this option on my instances that support
it. I recently tried upping the nodes to the latest generation (m3) to try
and rectify/improve this issue. Unfortunately right now m3 won't work
Is the instance ebs-optimized? I am wondering if its a configuration on the
instance not postgres or ebs.
On Wed, Oct 29, 2014 at 10:12 AM, jmcdonagh
wrote:
> Hi Tomas- thank you for your thoughtful response!
>
>
> Tomas Vondra wrote
> > On 28.10.2014 21:55, jmcdonagh wrote:
> >> Hi, we have a n
Hi Tomas- thank you for your thoughtful response!
Tomas Vondra wrote
> On 28.10.2014 21:55, jmcdonagh wrote:
>> Hi, we have a nightly job that restores current production data to
>> the development databases in a 'warm spare' database so that if the
>> developers need fresh data, it's ready durin
Jeff Chen wrote:
> One of these queries that should be targeting something like 300K
> photos takes 38 seconds to run (with an aggregate/nested loop
> taking effectively all of that time),
With the seek time of commodity disk drives typically being 9ms, a
naive approach using random access to jo
