Hello All,
Getting *ERROR: XX001: could not read block 17 of relation
base/16386/2619: read only 0 of 8192 bytes*, While vacuuming database
Manual vacuuming and Auto vacuuming process *constantly* taking high
CPU, not able to skip corrupted table for vacuuming and dump this
message at
Siddharth Shah wrote:
> * fsync is off*
If you are running the database with fsync off and there is any sort
of unusual termination, your database will probably be corrupted. I
recommend restoring from your last good backup. If you don't have
one, recovery is going to be painful; I recommend
Thanks Kevin.
Yes, I installed 8.4.3 then I have found that DDL and DML statements
were getting failed to execute in some distributions
So that's why taken call for reindexing
What can be the method to verify that it's a database corruption ?
xdb=# \dt;
ERROR: index "pg_class_relname_nsp_
[rearranged to put the most critical point first]
Siddharth Shah wrote:
> I don't have any backup available, Is there any way to fix this ?
I *strongly* recommend that you shut down the database and take a
file copy of the whole data tree (everything under what -D points to
on the server sta
hi,
i am a student , and for my final project i have to work with postgresql ;
my project subject is data warehousing & data mining, so i need to define
cube; create dimention table & fact table & ...
i had active cube in template1; i mean i run cube.sql and there are cube
functions in my databas
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0x201d2, order=0, oomkilladj=0
May 6 22:31:01 pgblade02 kernel:
May 6 22:31:01 pgblade02 kernel: Call Trace:
May 6 22:31:19 pgblade02 ke
Kevin Grittner wrote:
[rearranged to put the most critical point first]
Siddharth Shah wrote:
I don't have any backup available, Is there any way to fix this ?
I *strongly* recommend that you shut down the database and take a
file copy of the whole data tree (everything under wha
One more point, This is observed two times while product firmware
updates which updates Postgres 8.4.3 from 8.4.1
Abruptly shutdown never leads to this type of corruption while fsync is
always off
Thanks,
Siddharth
Siddharth Shah wrote:
Kevin Grittner wrote:
[rearranged to put the most cr
Silvio Brandani wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0x201d2, order=0, oomkilladj=0
May 6 22:31:01 pgblade02 kernel:
May 6 22:31:01 pgblade02 kernel: Call Trace:
May
Siddharth Shah wrote:
>>> xdb=# reindex index pg_class_relname_nsp_index;
>>>
>>> Now INDEXing taking High CPU and postgres baffled.
>> consider doing your recovery in single-user mode
> postgres --single -P -D $DATADIR -p 5433 xdb
> Same behavior in single mode.
How long did you l
On Fri, May 7, 2010 at 8:26 AM, Silvio Brandani wrote:
> We have a postgres 8.3.8 on linux
>
> We get following messages int /var/log/messages:
>
> May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
> gfp_mask=0x201d2, order=0, oomkilladj=0
>
*** snip ***
> May 6 22:31:30 pgblade02
Lacey Powers ha scritto:
Silvio Brandani wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0x201d2, order=0, oomkilladj=0
May 6 22:31:01 pgblade02 kernel:
May 6 22:31:01 pgblade0
Kevin Grittner wrote:
Siddharth Shah wrote:
xdb=# reindex index pg_class_relname_nsp_index;
Now INDEXing taking High CPU and postgres baffled.
consider doing your recovery in single-user mode
postgres --single -P -D $DATADIR -p 5433 xdb
Same behavior in
Greg Spiegelberg ha scritto:
On Fri, May 7, 2010 at 8:26 AM, Silvio Brandani
mailto:silvio.brand...@tech.sdb.it>> wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0
Silvio Brandani ha scritto:
Lacey Powers ha scritto:
Silvio Brandani wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0x201d2, order=0, oomkilladj=0
May 6 22:31:01 pgblade02 ker
Silvio Brandani ha scritto:
Greg Spiegelberg ha scritto:
On Fri, May 7, 2010 at 8:26 AM, Silvio Brandani
mailto:silvio.brand...@tech.sdb.it>>
wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invo
Siddharth Shah writes:
> PID PPID USER STAT VSZ %MEM %CPU COMMAND
> 13419 13418 nobody R39172 8% 99% postgres --single -P -D
> /var/db -p 5433 xdb
> It's been running from 10 minutes still there is no output or logs.
What does "strace" show that process is doing?
Silvio Brandani wrote:
Lacey Powers ha scritto:
Silvio Brandani wrote:
We have a postgres 8.3.8 on linux
We get following messages int /var/log/messages:
May 6 22:31:01 pgblade02 kernel: postgres invoked oom-killer:
gfp_mask=0x201d2, order=0, oomkilladj=0
May 6 22:31:01 pgblade02 kernel:
raha sadeghi wrote:
> i had active cube in template1; i mean i run cube.sql and there
> are cube functions in my databases but i don't know how to create
> cube!!!
> please help me and explain me how to do these kind of things step
> by step!!
Before anyone can make useful suggestions, I thin
19 matches
Mail list logo
