On Thu, 1 Dec 2005, Richard Huxton wrote:
Tatsumi Abe wrote:
Question is about the relation between fragmentation of file and VACUUM
performance.
OS:RedHat Enterprise Linux AS Release 3(Taroon Update 6)
Kernel 2.4.21-37.ELsmp on an i686
Filesystem Type ext3
Filesystem features: h
On Dec 1, 2005, at 00:50, Tatsumi Abe wrote:
However, In my current environment I can't stop PostgreSQL and cancel
fragmentation.
Could anyone advise some solutions for this fragmentation problem
without stopping PostgreSQL ?
This is somewhat of an aside and intended just as a helpful suggest
On Thu, Dec 01, 2005 at 02:50:56PM +0900, Tatsumi Abe wrote:
Could anyone advise some solutions for this fragmentation problem
without stopping PostgreSQL ?
Stop doing VACUUM FULL so often. If your table size is constant anyway
you're just wasting time by compacting the table and shrinking it,
Tatsumi Abe wrote:
> Question is about the relation between fragmentation of file and VACUUM
> performance.
>
>
> OS:RedHat Enterprise Linux AS Release 3(Taroon Update 6)
> Kernel 2.4.21-37.ELsmp on an i686
> Filesystem Type ext3
> Filesystem features: has_journal filetype needs_reco
Question is about the relation between fragmentation of file and VACUUM
performance.
OS:RedHat Enterprise Linux AS Release 3(Taroon Update 6)
Kernel 2.4.21-37.ELsmp on an i686
Filesystem Type ext3
Filesystem features: has_journal filetype needs_recovery sparse_super
large_file
CPU:I