From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: panic failed to add item |
Date: | 2009-11-20 23:14:47 |
Message-ID: | dcc563d10911201514ub0ff1b9m9379c81c9bbd3e21@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Nov 20, 2009 at 4:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
>> Access is pretty random actually, and fill factor on this database is
>> 100% because it doesn't really get updated, just appended to. There
>> are a lot of parallel insertions going on if that helps.
>
> Do you mean you actually have fillfactor set somewhere? It didn't show
> on the \d output.
No, I just assumed it was 100% still by default. Did that change?
> Is this a 32-bit or 64-bit machine?
64 bit. Centos / RHEL 5.3 running the -95 or so Centos 5.2 kernel
because later kernels cause problems with the Areca 1680 series RAID
array controller kicking offline at odd times
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Witt | 2009-11-21 01:16:21 | use log_statement to log only SELECTs? |
Previous Message | Tom Lane | 2009-11-20 23:03:09 | Re: panic failed to add item |