| From: | Seref Arikan <serefarikan(at)gmail(dot)com> |
|---|---|
| To: | François Beausoleil <francois(at)teksol(dot)info> |
| Cc: | Seref Arikan <serefarikan(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Disk space available, but getting error "could not write to hash-join temporary file: No space left on device" |
| Date: | 2014-08-10 13:48:49 |
| Message-ID: | CA+4ThdqQGXAu+i9MTUNzncQtLX==3hNAHRo=5FajqUfO-X46pw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
François,
How vry stupid of me, and how kind of you to point at the obvious thing I
was missing.
Best regards
Seref
On Sun, Aug 10, 2014 at 12:40 PM, François Beausoleil <francois(at)teksol(dot)info>
wrote:
>
> > Le 2014-08-10 à 06:31, Seref Arikan <serefarikan(at)gmail(dot)com> a écrit :
> >
> > Greetings,
> > A function aborts with the error in the subject line despite the
> available free space on the disk.
> > I have a bunch of other questions regarding the underlying reason but
> first things first: why is pg telling me no space is left on device when
> there is space?
> >
> > the only config param I can see relevant to this is temp_file_limit
> which I've set to -1, but it made no difference. How can I make sure that
> as long as there is disk space available, I don't get this error?
>
> When have you checked? Because the JOIN might use lots of disk space, then
> the transaction aborts and when you check, there is free space.
>
> Hope that helps,
> François
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2014-08-10 23:10:59 | pg_advisory_lock problem |
| Previous Message | François Beausoleil | 2014-08-10 11:40:48 | Re: Disk space available, but getting error "could not write to hash-join temporary file: No space left on device" |