Hi Mark
Thanks for your suggestions (and Robert and Guillaume). I will try the
overcommit_memory=2 idea out in a couple of weeks. At the moment I am
running everything on 8.4.8, which is working great, and have pressing
deadlines looming (next Wednesday).
I'll let you know when I do. I want t
On 28/10/11 15:42, Finlay Thompson wrote:
After upgrading the postgresql*-8.4 packages on ubuntu, to version 8.4.9,
the script suddenly stopped working, and consuming all the ram (16GB) on the
computer (i7).
If there is one query exhausting all ram, then it could be tricky to
catch it in the
On Mon, Oct 31, 2011 at 1:50 PM, Robert Haas wrote:
> If you can't do that for some reason, there's always auto_explain, but
> that has some overhead and is a bit more work to set up.
If it's a massive load of data with a lot of queries, I think his best
bet is to log the queries with log_min_dur
On Sun, Oct 30, 2011 at 10:30 PM, Finlay Thompson
wrote:
> Hi Tom
>
> Sorry for the delay.
>
> The version of postgis didn't change, and when I rolled back to
> postgresql 8.4.9 the expected performance returned. I am very confident
> the regression was caused by the 8.4.9 upgrade.
>
> Any suggest
Hi Tom
Sorry for the delay.
The version of postgis didn't change, and when I rolled back to
postgresql 8.4.9 the expected performance returned. I am very confident
the regression was caused by the 8.4.9 upgrade.
Any suggestions on how to diagnose a long run script like this ? I can
easily turn
"Finlay Thompson" writes:
> After an upgrade from 8.4.8 to 8.4.9 performance of load script went from ~
> 3 hours to not finishing after 24 hours.
> Context: We have a continuous build script, that loads, grooms, matches data
> every few hours. The script has been run over 100 times in the last f
The following bug has been logged online:
Bug reference: 6275
Logged by: Finlay Thompson
Email address: fin...@dragonfly.co.nz
PostgreSQL version: 8.4.9
Operating system: Ubuntu 11.04
Description:Horrible performance regression
Details:
After an upgrade from 8.4.8 t
