On Fri, Mar 25, 2011 at 8:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Interesting, but I don't understand/believe your argument as to why this
> is a bad idea or fixed-size extents are better. It sounds to me just
> like the typical Oracle DBA compulsion to have a knob to twiddle. A
> self-adjusting enlargement behavior seems smarter all round.
So is it ok for inserting one row to cause my table to grow by 90GB?
Or should there be some maximum size increment at which it stops
growing? What should that maximum be? What if I'm on a big raid system
where that size doesn't even add a block to every stripe element?
Say you start with 64k (8 pg blocks). That means your growth
increments will be 64k, 70k, 77kl, 85k, 94k, 103k, 113k, 125k, 137k,
I'm having trouble imagining a set of hardware and filesystem where
growing a table by 125k will be optimal. The next allocation will have
to do some or all of a) go back and edit the previous one to round it
up, then b) add 128k more, then c) still have 6k more to allocate in a
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2011-03-25 21:34:52|
|Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full) |
|Previous:||From: DIEGO BALAN||Date: 2011-03-25 20:59:10|
|Subject: BUG #5951: ERRO NO INICIO DA INSTALACAO|