From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | nolan(at)celery(dot)tssi(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
Date: | 2003-10-09 06:42:24 |
Message-ID: | 3F850350.9010601@persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
nolan(at)celery(dot)tssi(dot)com wrote:
>>One of my friend lost data with mysql yesterday.. The machine was taken down for
>>disk upgrade and mysql apperantly did not commit the last insert.. OK he was
>>using myisam but still..:-)
>
>
> It sounds like that is more a problem with improper operating protocols
> than with the underlying database.
No. Problem is machine was shutdown with shutdown -h. It sends sigterm to
everybody. A good process would flsuh the buffers to disk before finishing.
Mysql didn't on that occasion.
Transactions or not, this behaviour is unacceptable for any serious app.
>
> Would PG know enough to do a commit regardless of how the database was
> shut down? A second question is whether doing a commit is what the user
> or application would always want to have happen, as it could result in a
> half-completed transaction.
Do a shutdown -h on a live database machine with pg. It will gracefully shut
itself down.
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | CSN | 2003-10-09 07:10:02 | autoupdate sequences after copy |
Previous Message | Nagib Abi Fadel | 2003-10-09 06:42:19 | Re: Cross database foreign key workaround? |