>>>>> "sm" == scott marlowe <scott.marlowe> writes:
>> 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. sm> While it is possible to lose a non-committed transaction, WAL prevents the sm> database from becoming corrupted. Assuming proper fsyncing of your hard sm> drives (i.e. SCSI, or IDE with write cache disabled) So you're saying it is not possible to corrupt the WAL if the process is ungracefully killed by the OS? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
