Henk - CityWEB <[EMAIL PROTECTED]> writes:
> On Thu, 21 Jun 2007, Tom Lane wrote:
>> FWIW, the only occurrences of that specific message text are in
>> PageIndexTupleDelete and PageIndexMultiDelete, so you can be pretty sure
>> that this is just a corrupted-index problem. Once you've identified
>>
On Thu, 21 Jun 2007, Tom Lane wrote:
> "Henka" <[EMAIL PROTECTED]> writes:
> > I happened to notice this error in the log when my application was refused
> > a db connection (quite unexpectedly):
>
> > PANIC: corrupted item pointer: offset = 3308, size = 28
> > LOG: autovacuum process (PID 181
Henk - CityWEB wrote:
> I can't wait to get a decent master/multi-slave setup going where I can
> turn fsync on and still get semi-decent performance...
I don't see how replication can help you with fsync performance
problems. Controllers with battery backed write cache are cheap. What is
the poin
On Thu, 21 Jun 2007, Gregory Stark wrote:
> Ugh. The worst part is that you won't even know that there's anything wrong
> with your data. I would actually suggest that if you run with fsync off and
> have a power failure or kernel crash you should just immediately restore from
> your last backup
On Thu, 21 Jun 2007, Tom Lane wrote:
> "Henka" <[EMAIL PROTECTED]> writes:
> > I happened to notice this error in the log when my application was refused
> > a db connection (quite unexpectedly):
>
> > PANIC: corrupted item pointer: offset = 3308, size = 28
> > LOG: autovacuum process (PID 1816
"Henka" <[EMAIL PROTECTED]> writes:
> I happened to notice this error in the log when my application was refused
> a db connection (quite unexpectedly):
> PANIC: corrupted item pointer: offset = 3308, size = 28
> LOG: autovacuum process (PID 18165) was terminated by signal 6
FWIW, the only occu
"Henka" <[EMAIL PROTECTED]> writes:
>> Other than that it might be interesting to know the values of some server
>> parameters: "fsync" and "full_page_writes". Have you ever had this machine
>> crash or had a power failure? And what kind of i/o controller is this?
>
> fsync = off
> full_page_writ
>> I'm using PG 8.2.3:
>
> You should update to 8.2.4, it includes a security fix and several bug
> fixes.
That was my next option. My last backup dump looks suspiciously small,
but the day before that looks about right.
> My first thought is bad memory. It's always good to rule that out sinc
"Henka" <[EMAIL PROTECTED]> writes:
> Hello all,
>
> I'm using PG 8.2.3:
You should update to 8.2.4, it includes a security fix and several bug fixes.
However afaik none of them look like this.
> PANIC: corrupted item pointer: offset = 3308, size = 28
> LOG: autovacuum process (PID 18165) was
Hello all,
I'm using PG 8.2.3:
PostgreSQL 8.2.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.6
I happened to notice this error in the log when my application was refused
a db connection (quite unexpectedly):
PANIC: corrupted item pointer: offset = 3308, size = 28
LOG: autovacuum proces
10 matches
Mail list logo
