From: | Mike Christensen <imaudi(at)comcast(dot)net> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: When adding millions of rows at once, getting out of disk space errors |
Date: | 2009-02-18 21:14:01 |
Message-ID: | 499C7A19.4030000@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ooo good call, the account is part of the "Users" group which has a quota:
The users will have the following disk quota:
Disk space limited to 1024 MB
Warning sent at 900 MB
Which is the exact size of the database..
However, anyone have a clue on how to change this? This is Windows
Server 2003 SBS, I'm not an expert <g>
Bill Moran wrote:
> In response to Mike Christensen <imaudi(at)comcast(dot)net>:
>
>
>> I have well over 50 gigs free on that drive.. I doubt it.
>>
>
> I'm not aware of that error having false-positives associated with it.
>
> Common confusion on this point could result from having quotas enabled,
> or possibly you're running out of space, then when you check free space
> (after the error has occurred) the space has already been reclaimed from
> the failed transaction and therefore it looks like you have plenty of
> free space, but it disappears when you're running the process.
>
> Also, 2x check that Postgres' data files are on the same partition as
> where you've got the 50G free (I've made that mistake more than once)
>
> If none of those help, provide more details. Based on the detail level
> you've provided, you've run out of disk space.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-18 21:16:06 | Re: Appending \o output instead of overwriting the output file |
Previous Message | Sam Mason | 2009-02-18 21:09:57 | Re: When adding millions of rows at once, getting out of disk space errors |