Jeff,
Sorry for the delayed response. Please see (some) answers inline.
On 12/1/2011 9:06 AM, Jeff Janes wrote:
> On Wed, Nov 30, 2011 at 7:27 AM, Benjamin Johnson
> wrote:
>> Experts,
>>
>> Quick Summary: data can now be inserted very quickly via COPY + removing
&g
ead of HD for the indexes
> only (that is, having the indexes in a separate tablespace of ssds). The
> problem is that your disks usually can't keep up with the number of
> random writes it takes to update N "random values" btrees; ssd might help.
> Can you post some numbers, such as # of indexes, # of rows you're trying
> to insert per hour etc etc?
>
>
--
Benjamin Johnson
http://getcarbonblack.com/ | @getcarbonblack
cell: 312.933.3612
bly have hourly tables for today and as soon as we
can try to re-add indexes. Another possible solution might be to stream
the data to another "reader" postgres instance that has indexes,
although I'm not very versed in replication.
Any ideas would be greatly appreciated.
Thanks!
Be
