Yes, that was it Michael. I increased my working memory which helped
(although it was still writing to a temp table), and also split the
query into smaller bits. THanks.
On 5 February 2014 20:39, Michael Wood <esiotrot@gmail.com> wrote:
> On 31 Jan 2014 4:51 PM, "James David Smith" <james.david.smith@gmail.com>
> wrote:
>>
>> Hi Kevin / all,
>>
>> I tried to run the update with your code but got the following error
>> (which I realise is now diverging from my original question):
>>
>> ERROR: could not write to hash-join temporary file: No space left on
>> device
>> ********** Error **********
>
> Just a guess, but maybe it's writing to a temporary table and ran out of
> disk space?
>
>> Any thoughts? I didn't tweak the memory allocation or cost factors
>> before I ran it - maybe that would help? I didn't bother doing it
>> initially as I wasn't too fussed if it took say 4 hours instead of 3
>> etc. I'm not in a huge rush.
>>
>> Regarding the system, it's a virtual Ubuntu 12.04 desktop with
>> PostgreSQL 9.3 and PostGIS 2.0. I asked our IT guy for the details
>> about it and he gave the below. I'm the only user of the visualization
>> set-up at the moment, so all the resource *should* be available to me
>> he says:
>>
>> 20 cores of Intel Xeon E-2690 v2 processor @ 3GHz
>> 48GB of memory at 1866 MHz
>> Hard drive based on 10 x 15K RPM SAS hard disks
>>
>> Cheers
>>
>> James
>
> --
> Michael Wood
