| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, Y Sidhu <ysidhu(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Disk Fills Up and fsck "Compresses" it |
| Date: | 2007-05-16 23:28:30 |
| Message-ID: | 464B939E.8090402@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jim C. Nasby wrote:
> No, it's part of FreeBSD's UFS. google FreeBSD softupdates and you
> should get plenty of info.
>
> As I said, it's probably not worth worrying about.
>
> On Wed, May 16, 2007 at 08:21:23AM -0700, Y Sidhu wrote:
>> What do you mean by "softupdates?" Is that a parameter in what I am guessing
>> is the conf file?
Here is quite a good article on the interaction of fsck and softupdates
in FreeBSD:
http://www.usenix.org/publications/library/proceedings/bsdcon02/mckusick/mckusick_html/index.html
Having said that, it seems to talk about space lost by unreferenced
blocks and inodes is the context of panic or power outage, as opposed to
normal softupdate operation (unless I'm missing something...)
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Shelukhin | 2007-05-17 05:42:27 | any way to get rid of Bitmap Heap Scan recheck? |
| Previous Message | Tom Lane | 2007-05-16 21:30:51 | Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal |