| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: REINDEX takes half a day (and still not complete!) |
| Date: | 2011-04-18 06:39:58 |
| Message-ID: | BANLkTik22uXgKenA9Tst-bhNVU6aC=6unw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Apr 18, 2011 at 7:14 AM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> # REINDEX INDEX new_idx_userid;
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
>
>
> What else could be wrong?
That's hardly enough information to guess, but since we're trying to
guess, maybe your maintainance_mem went overboard and your server ran
out of RAM. Or disk space.
Aside from a bug, that's the only reason I can think for a pg backend
to bail out like that. Well, the connection could have been cut off by
other means (ie: someone tripped on the cable or something), but lets
not dwell on those options.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2011-04-18 06:42:08 | Re: REINDEX takes half a day (and still not complete!) |
| Previous Message | Phoenix Kiula | 2011-04-18 05:19:03 | Re: REINDEX takes half a day (and still not complete!) |