| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Mike Christensen <imaudi(at)comcast(dot)net> |
| Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: When adding millions of rows at once, getting out of disk space errors |
| Date: | 2009-02-19 10:41:04 |
| Message-ID: | dcc563d10902190241y75ff9f29i6b0341e0e45ef916@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 19, 2009 at 3:11 AM, Mike Christensen <imaudi(at)comcast(dot)net> wrote:
> Actually I'm writing emails on my Mac <g>
>
> However, the Postgres service is running on my Windows 2003 machine..
>
> The disk space issue turned out to be a disk quota which was easy to solve.
> Unfortunately, the fact it crashed Postgres and with a massive transaction
> log left the server in a state where it wouldn't boot anymore. I was
> eventually able to fix it by resetting the transaction log manually. I'm
> hoping future versions of Postgres will handle this scenario a lot better..
They're certainly supposed to. I've had no such problems running out
of space on linux in the past. I wonder if it's a windows thing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. Kretschmer | 2009-02-19 10:50:32 | Re: Accessing array elements in a FOR PL/pgsql loop |
| Previous Message | Igor Katson | 2009-02-19 10:36:35 | Accessing array elements in a FOR PL/pgsql loop |