| From: | Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com> |
|---|---|
| To: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dumping and reloading stuff in 6.5.3 |
| Date: | 2000-05-15 14:12:25 |
| Message-ID: | 392005C9.6C51D6CF@cupid.suninternet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Lincoln Yeoh wrote:
>
> Actually, say if I use postgresql on a journalling file system, would this
> problem go away? e.g. I just lose data not written, but the database will
> be at a known uncorrupted state, consistent with logs.
Hmm, someone may have to correct me on this but last time I checked all
the
journalling filesystems currently available journalled *filesystem*
*metadata*. IOW, after a crash, the filesystem structure will be intact,
but your database maybe completely corrupt.
Anyway, how does the filesystem driver know what is a consistant state
for the database? For that postgres would have to do it's own
journalling,
right?
--
Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com>
http://cupid.suninternet.com/~kleptog/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2000-05-15 14:15:43 | Re: Best way to "add" columns |
| Previous Message | Web Manager | 2000-05-11 19:14:11 | Re: AGAIN: Linking data across databases |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-15 14:15:53 | Re: Dumping and reloading stuff in 6.5.3 |
| Previous Message | Tom Lane | 2000-05-15 14:11:04 | Re: AW: type conversion discussion |