Am 06.04.2012 23:49, schrieb Jeff Davis:
No, i didn't found any in my postgresql dirs. Should i have a core file
around when i see a segmentation fault? What should i look for?
It's an OS setup thing, but generally a crash will generate a core file
if it is allowed to. Use ulimit -c
On Sat, 2012-03-31 at 13:21 +0200, Janning Vygen wrote:
The OS was installed a few days before, the i installed the postgresql
instance. I configured my setup with a backup server by WAL archiving.
Then i tested some things and i played around with pg_reorg (but i
didn't use ist till then)
Thank you so much for still helping me...
Am 30.03.2012 20:24, schrieb Jeff Davis:
On Fri, 2012-03-30 at 16:02 +0200, Janning Vygen wrote:
The PANIC occurred first on March, 19. My servers uptime ist 56 days, so
about 4th of February. There was no power failure since i started to use
this
Hi,
thanks so much for answering. I found a segmentation fault in my logs
so please check below:
On Tue, 2012-03-27 at 11:47 +0200, Janning Vygen wrote:
I am running postgresql-9.1 from debian backport package fsync=on
full_page_writes=off
That may be unsafe (and usually is) depending
On Fri, 2012-03-30 at 16:02 +0200, Janning Vygen wrote:
The PANIC occurred first on March, 19. My servers uptime ist 56 days, so
about 4th of February. There was no power failure since i started to use
this machine. This machine is in use since March, 7. I checked it twice:
Now power failure.
Hi,
First of all, shut down both servers (you indicated that you have a
replica) and make a full copy of both data directories. At the first
sign of corruption, that's always a good step as long as it's a
practical amount of data (obviously this is more of a challenge if you
have terabytes of
Hi,
I am running postgresql-9.1 from debian backport package
fsync=on
full_page_writes=off
I didn't had any power failures on this server.
Now I got this:
1. Logfile PANIC
postgres[27352]: [4-1] PANIC: corrupted item pointer: offset = 21248,
size = 16
postgres[27352]: [4-2] STATEMENT: insert
On 05/14/2010 07:16 PM, Emanuel Calvo Franco wrote:
The PANIC happens several times per minute, so, is really bad for me.
I tried to narrow down based on a field (timestamp) and I found some bad
points, but I cannot delete them (same PANIC message appear).
Do you have any idea how can I
On 05/14/2010 08:49 PM, Igor Neyman wrote:
-Original Message-
From: Catalin BOIE [mailto:cboie-pg...@66.com]
Sent: Friday, May 14, 2010 5:43 AM
To: pgsql-general@postgresql.org
Subject: Re: PANIC: corrupted item pointer: 32766
Some more info.
The PANIC happens several times
Hello!
I have a serious problem with one of my tables.
Version: postgresql-server-8.4.3-1.fc12.x86_64
Kernel: kernel-2.6.32.11-99.fc12.x86_64
I reindexed all indexes on that table, but I still cannot workaround
this problem.
Memory is ECC and the storage is RAID10 (BIOS reported it OK).
How I
Some more info.
The PANIC happens several times per minute, so, is really bad for me.
I tried to narrow down based on a field (timestamp) and I found some bad
points, but I cannot delete them (same PANIC message appear).
Do you have any idea how can I correct that entries?
The worry part is
The PANIC happens several times per minute, so, is really bad for me.
I tried to narrow down based on a field (timestamp) and I found some bad
points, but I cannot delete them (same PANIC message appear).
Do you have any idea how can I correct that entries?
The worry part is how this
-Original Message-
From: Catalin BOIE [mailto:cboie-pg...@66.com]
Sent: Friday, May 14, 2010 5:43 AM
To: pgsql-general@postgresql.org
Subject: Re: PANIC: corrupted item pointer: 32766
Some more info.
The PANIC happens several times per minute, so, is really bad for me.
I
Excerpts from Catalin BOIE's message of vie may 14 02:32:01 -0400 2010:
Hello!
I have a serious problem with one of my tables.
Version: postgresql-server-8.4.3-1.fc12.x86_64
Kernel: kernel-2.6.32.11-99.fc12.x86_64
Hmm, it's pretty unfortunate that those buffer checks are inside
14 matches
Mail list logo
