rwrite only the updated column,
the performance difference between Oracle and PG in that case may be
significant.
I researched about this issues in mailing list and google.
But I've not found anything related to this issues.
Thank you.
Kisung Kim.
(C)Bitnine, Kisung Kim, Ph.D
https://s
2015-10-26 11:12 GMT+09:00 Michael Paquier :
>
>
> On Mon, Oct 26, 2015 at 10:52 AM, Kisung Kim wrote:
>
>> Because of the internal implementation of MVCC in PG
>> the update of a row is actually a insertion of a new version row.
>> So if the size of a row is huge
which I think of not a good solution.
2015-11-24 8:12 GMT+09:00 Chapman Flack :
> Has anyone got the stomach to try such a thing and see what happens?
> I don't have MSVC here.
>
> -Chap
We have the environment to test your ideas.
Can you explain your ideas with more detail?
workload (only insert),
then is there any chances to improve PG's index behavior.
Thank you very much.
--
Bitnine Global Inc., Kisung Kim, Ph.D
https://sites.google.com/site/kisungresearch/
E-mail : ks...@bitnine.net
Office phone : 070-4800-5890, 408-606-8602
US Mobile phone : 408-805-2192
l
and leaf_pages and make more dense leaf pages.
On Wed, Aug 10, 2016 at 6:47 PM, Lukas Fittl wrote:
> On Wed, Aug 10, 2016 at 4:24 PM, Kisung Kim wrote:
>>
>> When I used the index bloating estimation script in
>> https://github.com/ioguix/pgsql-bloat-estimation,
>>
5 to 3 GB - does that really help
> performance significantly?
>
> regards
>
> Mark
>
>
> On 11/08/16 16:08, Kisung Kim wrote:
>
>> Thank you for your information.
>> Here is the result:
>>
>> After insertions:
>>
>> ycsb=# select
