On Wed, Aug 17, 2016 at 6:45 AM, pinker wrote:
> Hi,
> the problem I'm dealing with is long holding locks during extensions of
> table:
> process xxx still waiting for ExclusiveLock on extension of relation xxx of
> database xxx after 3000.158 ms
> My application is write intensive, in one round I
On 8/18/16 5:26 PM, pinker wrote:
1. rename table t01 to t02
OK...
2. insert into t02 1M rows in chunks for about 100k
Why not just insert into t01??
Because of cpu utilization, it speeds up when load is divided
That still doesn't explain why you renamed t01 to t02.
3. from t01 (previo
2016-08-18 21:40 GMT+03:00 Victor Yegorov :
> Oh, that's interesting. I was under impression, that r_p_c reflects IO
> speed, like — make it smaller for SSDs.
> To make this query prefer BitmapScan, I need to bump r_p_c to 5.8. And 6.0
> makes it switch to SeqScan.
>
I was looking into different
2016-08-18 23:06 GMT+03:00 Jeff Janes :
> It does account for them, but perhaps not perfectly. See "[PERFORM]
> index fragmentation on insert-only table with non-unique column" for
> some arguments on that which might be relevant to you.
>
Thanks for pointing this out, good stuff to know.
If y
