Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
TIA
--
Jord Tanner <jo**@indygecko.com>
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
8  1505 
On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
--
Jord Tanner <jo**@indygecko.com>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
--
Jord Tanner <jo**@indygecko.com>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
Are you running the megaraid 2 driver or the older 1.18 series? Just
wondering.
On Wed, 21 Apr 2004, Jord Tanner wrote:
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Are you running the megaraid 2 driver or the older 1.18 series? Just
wondering.
On Wed, 21 Apr 2004, Jord Tanner wrote:
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
Greetings,
Does anyone know what the effect of sending an INT signal (kill -2) to
each of:
- pg backend
- psql running an insert or select into
- Perl script with DBI connection to pg, running insert or
select into
- vacuumdb
I'm getting some database corruption, and I'm wondering if the use of
'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
On Wed, 2004-04-21 at 15:19, scott.marlowe wrote: Are you running the megaraid 2 driver or the older 1.18 series? Just
wondering.
We started with the megaraid driver distributed with 2.6.3, which is
megaraid v2.00.3. With that driver we weren't able to insert more than 5
million row before corruption appeared. After upgrading to megaraid
v2.20.B2 and 2.6.5 things ran much better, but we are still able to get
the occational DB corruption, though we now have one table with 27
million rows which is working correctly, however, another smaller table
is still problematic. We were running XFS on LVM2 on linux RAID0 on
megaraid RAID1. I switched to JFS, and we are continuing to test.
I'm fairly confident that the problem is the bleeding edge 64bit compile
we are running, and not an underlying hardware problem, but I have to
look at everything.
On Wed, 21 Apr 2004, Jord Tanner wrote:
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
>
> Greetings,
>
> Does anyone know what the effect of sending an INT signal (kill -2) to
> each of:
> - pg backend
> - psql running an insert or select into
> - Perl script with DBI connection to pg, running insert or
> select into
> - vacuumdb
>
> I'm getting some database corruption, and I'm wondering if the use of
> 'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
--
Jord Tanner <jo**@indygecko.com>
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
On Wed, 2004-04-21 at 15:19, scott.marlowe wrote: Are you running the megaraid 2 driver or the older 1.18 series? Just
wondering.
We started with the megaraid driver distributed with 2.6.3, which is
megaraid v2.00.3. With that driver we weren't able to insert more than 5
million row before corruption appeared. After upgrading to megaraid
v2.20.B2 and 2.6.5 things ran much better, but we are still able to get
the occational DB corruption, though we now have one table with 27
million rows which is working correctly, however, another smaller table
is still problematic. We were running XFS on LVM2 on linux RAID0 on
megaraid RAID1. I switched to JFS, and we are continuing to test.
I'm fairly confident that the problem is the bleeding edge 64bit compile
we are running, and not an underlying hardware problem, but I have to
look at everything.
On Wed, 21 Apr 2004, Jord Tanner wrote:
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).
Thanks for the feedback. I'm just covering all the bases.
Jord Tanner
On Wed, 2004-04-21 at 12:59, scott.marlowe wrote: On Wed, 21 Apr 2004, Jord Tanner wrote:
>
> Greetings,
>
> Does anyone know what the effect of sending an INT signal (kill -2) to
> each of:
> - pg backend
> - psql running an insert or select into
> - Perl script with DBI connection to pg, running insert or
> select into
> - vacuumdb
>
> I'm getting some database corruption, and I'm wondering if the use of
> 'kill -2' could be the cause.
No, kill -2 should not cause corruption.
About once a month we get someone on the lists getting corruption. almost
every time it's either a bad hard drive, memory, or system/cpu/mobo
causing it. Have you tested your memory (memtest86) or drives (badblocks
on linux) to make sure they aren't the cause of your problem? Just
because a server is new doesn't mean it's free of all flaws.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
--
Jord Tanner <jo**@indygecko.com>
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Bob Swerdlow |
last post by:
My application starts up a number of processes for various purposes using:
self.popen = popen2.Popen3("/usr/local/bin/python -O "myscript.py")
and then shuts them down when appropriate with...
|
by: Alex Hunsley |
last post by:
I'm running a monitoring script under linux written in python. It's nohup'ed so
that I can log out and it will continue running happily and so on, but
sometimes I need to kill the script before...
|
by: Vilmar Brazão de Oliveira |
last post by:
HI people,
what is wrong in the code bellow to kill iexplore.exe process after
processing my page??
'»»Before comes routines to access data base and to send email.
Set objWshell =...
|
by: Fred |
last post by:
There is a setting in INIT.ORA that has the unintended side-effect of
making sure the ALTER SYSTEM KILL SESSION command has immediate affect.
Without this setting, I've seen some instances where...
|
by: Micky |
last post by:
Can any one give me some pointers on how to kill a running procedure
in DB2? I have a long running procedure called from a Java routine and
after I kill the Java routine, the procedure keeps...
|
by: Alexander N. Spitzer |
last post by:
I am trying to write a program that will fork a process, and execute the
given task... the catch is that if it runs too long, I want to clean it up.
this seemed pretty straight forward with a...
|
by: WATYF |
last post by:
This is my problem... I have some code that starts a Process and
returns it to a variable... (prcBat)
At any time while that process is running... I want to be able to Kill
it by pressing a...
|
by: elrondrules |
last post by:
Hi
Am new to python and need your help!!
this is my code snip.
within my python script I have the following commands..
<snip>
import os
|
by: Richard Rossel |
last post by:
Hi Fellows,
I have a problem with process termination. I have a python code that
apache runs through a django interface.
The code is very simple, first, it creates a process with the...
|
by: spectrumdt |
last post by:
Hello.
I am running Fedora Linux and KDE, using the Konsole command line.
When coding Python, I regularly make a bug causing my program to not
terminate. But how do I kill the non-terminating...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| |
