pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: pginfo <pginfo@t1.unisoftbg.com>
Cc: Richard_D_Levine@raytheon.com, Michael Glaesemann <grzm@myrealbox.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-sql-owner@postgresql.org
Subject: Re: pg primary key bug?
Date: Thu, 17 Feb 2005 14:01:40 -0500
Message-ID: <9785.1108666900@sss.pgh.pa.us> (raw)
In-Reply-To: <4214D5C3.4070107@t1.unisoftbg.com>
References: <OFEF67063C.F61988F3-ON05256F9D.005A91D6@ftw.us.ray.com>
	<4214B466.20908@t1.unisoftbg.com>
	<8125.1108661189@sss.pgh.pa.us>
	<4214C94F.2050806@t1.unisoftbg.com>
	<9340.1108664352@sss.pgh.pa.us>
	<4214D5C3.4070107@t1.unisoftbg.com>

pginfo <pginfo@t1.unisoftbg.com> writes:
> Will upgrade to 8.0 solve this type of problems ?

The problem is probably not Postgres' fault at all.  I'm wondering about
disks with write cacheing enabled.  And you didn't turn off fsync,
I trust?

			regards, tom lane

view thread (27+ messages)  latest in thread

Message-ID: <9785.1108666900@sss.pgh.pa.us>
Permalink:  ../9785.1108666900@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/9785.1108666900@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pginfo@t1.unisoftbg.com, grzm@myrealbox.com, pgsql-sql-owner@postgresql.org
  Subject: Re: pg primary key bug?
  In-Reply-To: <9785.1108666900@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox