From: | Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Scott Marlowe <smarlowe(at)qwest(dot)net> |
Cc: | lec <limec(at)streamyx(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Losing records when server hang |
Date: | 2004-08-09 03:26:57 |
Message-ID: | 20040809032657.GA4827@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 08, 2004 at 08:36:36PM -0600, Scott Marlowe wrote:
> On Sun, 2004-08-08 at 19:43, lec wrote:
> > If I commit the following records 1,2,3,4,5,6,7,8,9,10 to the database
> > and the server hangs, I could lose records 5,6,7,8,9 but record 10 is
> > there. How is this possible and do anyone know how Postgresql
> > physically writes the records?
>
> Assuming a properly function storage subsystem and a kernel that does
> not lie about fsync, this is not possible.
It is actually possible if he uses several backends to do the job, and
transaction inserting record 10 commits before the hang, and 5,6,7,8,9
don't.
If this is only one backend, then I'd love to see how did he do that.
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"The ability to monopolize a planet is insignificant
next to the power of the source"
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-08-09 03:31:27 | Re: PostgreSQL 7.4.2 allows foreign key violation |
Previous Message | Dan Ruthers | 2004-08-09 03:18:29 | BIGINT indexes still with problems |