I seem that a failed vmotion occured in the same time frame.
Thanks for the help.
> Shut down the corrupted database and make a physical backup of it.
>
I did it before trying anything.
> Check the disks and memory on the machine where the problem occurred.
>
We are using virtual machines (VMWare). I will ask then to investigate
anyway.
> You can
Benoit Lobréau wrote:
> One of my PostgreSQL server crashed badly yesterday. A process was killed
> (see dmesg below) and postgres was stuck with theses process:
>
> postgres 2083 1 0 Oct08 ? 00:19:02
> /usr/lib/postgresql/9.5/bin/postgres -D /home/postgres/data/i090/systeme
>
Hi,
One of my PostgreSQL server crashed badly yesterday. A process was killed
(see dmesg below) and postgres was stuck with theses process:
postgres 2083 1 0 Oct08 ?00:19:02
/usr/lib/postgresql/9.5/bin/postgres -D /home/postgres/data/i090/systeme
postgres 2221 2083 0 Oct08 ?
On Tue, Mar 24, 2015 at 12:49 PM, Bankim Bhavsar
ban...@nimblestorage.com wrote:
Hello postgres experts,
We are running a test that periodically abruptly kills postgres
process(equivalent to kill -9) and restarts it.
After running this test for 24 hrs or so, we see duplicate primary key
.
From: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org]
on behalf of Kevin Grittner [kgri...@ymail.com]
Sent: Tuesday, March 24, 2015 12:47 PM
To: John R Pierce; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Index corruption
John R Pierce pie...@hogranch.com wrote:
On 3
On Tuesday, March 24, 2015, Bankim Bhavsar ban...@nimblestorage.com wrote:
Hello postgres experts,
We are running a test that periodically abruptly kills postgres
process(equivalent to kill -9) and restarts it.
After running this test for 24 hrs or so, we see duplicate primary key
entries
On 3/24/2015 12:05 PM, Bankim Bhavsar wrote:
We'll upgrade to 9.2.10 and attempt to reproduce the issue.
If possible, can someone point to corruption related issues fixed
after 9.2.0?
in the postgres manual, see the release notes for 9.2.1 through 9.2.10
--
john, recycling bits in santa
John R Pierce pie...@hogranch.com wrote:
On 3/24/2015 12:05 PM, Bankim Bhavsar wrote:
If possible, can someone point to corruption related issues fixed
after 9.2.0?
in the postgres manual, see the release notes for 9.2.1 through 9.2.10
You can find links to those from here:
On 3/24/2015 11:49 AM, Bankim Bhavsar wrote:
- 9.2.0
9.2 is currently at 9.2.10. 9.2.0 was released 2.5 years ago. several
of the bugs fixed in the 10 incremental updates were data corruption
related.
--
john, recycling bits in santa cruz
--
Sent via pgsql-general mailing list
Hello postgres experts,
We are running a test that periodically abruptly kills postgres
process(equivalent to kill -9) and restarts it.
After running this test for 24 hrs or so, we see duplicate primary key
entries in postgres table.
We detect this as we load internal hash-table
Thanks for the input.
We'll upgrade to 9.2.10 and attempt to reproduce the issue.
If possible, can someone point to corruption related issues fixed after
9.2.0?
Thanks,
-Bankim.
On 03/24/2015 11:56 AM, David G. Johnston wrote:
On Tuesday, March 24, 2015, Bankim Bhavsar
We moved to PostgreSQL about 2 years ago and have been very happy with it
overall. The only major issue that we've had is intermittent index corruption.
This manifests itself as either duplicate key value violates unique constraint
or could not read block 37422 of relation 1663/18663/19063: read
Dylan Adams dylan.adams.w...@gmail.com writes:
[ persistent occurrences of index corruption ]
My primary question: is this normal?
No. It does sound like you're managing to tickle some bug or other.
Can you extract a test case of any kind? We could fix it if we could
see it happening, but
Hi. Do you have triggers on corrupted tables?
2011/9/12, Dylan Adams dylan.adams.w...@gmail.com:
We moved to PostgreSQL about 2 years ago and have been very happy with it
overall. The only major issue that we've had is intermittent index
corruption.
This manifests itself as either duplicate
On Mon, Sep 12, 2011 at 9:41 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Dylan Adams dylan.adams.w...@gmail.com writes:
[ persistent occurrences of index corruption ]
My primary question: is this normal?
No. It does sound like you're managing to tickle some bug or other.
Can you extract a test
2011/9/12 pasman pasmański pasma...@gmail.com:
Hi. Do you have triggers on corrupted tables?
I haven't checked all the occurences, but at least some of the tables
that have had corrupted index have no triggers.
dylan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
On 9/12/2011 1:10 PM, Dylan Adams wrote:
On Mon, Sep 12, 2011 at 9:41 AM, Tom Lanet...@sss.pgh.pa.us wrote:
Dylan Adamsdylan.adams.w...@gmail.com writes:
[ persistent occurrences of index corruption ]
My primary question: is this normal?
No. It does sound like you're managing to tickle
On Mon, Sep 12, 2011 at 1:20 PM, Andy Colson a...@squeakycode.net wrote:
On 9/12/2011 1:10 PM, Dylan Adams wrote:
On Mon, Sep 12, 2011 at 9:41 AM, Tom Lanet...@sss.pgh.pa.us wrote:
Dylan Adamsdylan.adams.w...@gmail.com writes:
[ persistent occurrences of index corruption ]
My primary
On Mon, Sep 12, 2011 at 8:03 AM, Dylan Adams dylan.adams.w...@gmail.com wrote:
We moved to PostgreSQL about 2 years ago and have been very happy with it
overall. The only major issue that we've had is intermittent index corruption.
This manifests itself as either duplicate key value violates
On Mon, Sep 12, 2011 at 3:51 PM, Scott Marlowe scott.marl...@gmail.com wrote:
Are you sure you aren't having either server or RAID problems of some
kind? Single bit memory errors or bad sectors not getting remapped
before corrupting data etc? Have you torture tested your hardware to
ensure
21 matches
Mail list logo
