On Tue, Oct 2, 2012 at 5:54 PM, Craig Ringer wrote:
> On 10/02/2012 05:24 AM, Colin Taylor wrote:
>
>> My thoughts are: surely 0-row updates dont cause this or have impact on
>> the vacuum. I'm still doing the same updates after all why have things
>> degenerated so
Hi, previously I selected categorized data for update then updated counts
or inserted a new record if it was a new category of data.
select all categories
update batches of categories
or insert batches [intermingled as they hit batch size]
Problem was the select was saturating the network (pullin
Hi there, we've partioned a table (using 8.2) by day due to the 50TB of
data (500k row size, 100G rows) we expect to store it in a year.
Our performance on inserts and selects against the master table is
disappointing, 10x slower (with ony 1 partition constraint) than we get by
going to the part
Hi there,
I'm doing an update of ~30,000 rows and she takes about 15mins on
pretty good hardware, even just after a vacuum analyze.
I was hoping some kind soul could offer some performance advice. Do I
just have too many indexes? Or am I missing some trick with the nulls?
MY QUERY
updat
