Yes, but at least with transactions when the machine comes back up
you'll be in a consistant state. Ie: postgres will know the transaction
didn't finish, and should rollback what it was doing, when it starts up
again.
Without transactions you don't know if half of your operation completed
or all of it or etc.. pretty dangerous state to have your data in.
Or... at least this is now I understand it.
Jeff.
On Thu, 2003-10-09 at 14:30, Vivek Khera wrote:
> >>>>> "SD" == Shridhar Daithankar <shridhar_daithankar@persistent.co.in> writes:
>
> SD> Do a shutdown -h on a live database machine with pg. It will
> SD> gracefully shut itself down.
>
>
> I think it is a timing issue. The PG has no way to notify the OS that
> it has finished exiting, so if it takes a long time to exit, the OS
> will ungracefully kill the DB process(es). Doesn't matter what DB (or
> any other application) you're running, you *can* lose data this way.
