TOAST Fields serialisation/deserialization performance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Gents,

I have a few queries regarding the TOAST Fields serialisation/deserialization performance.

The use case i am trying to solve here is to have millions of partitions and aggregate the data in array field.

I wish to know if i declare certain column in table as "array of UDT/JSONB" and enable either lz4 or zstd compression on it, does appending or prepending to that array or even changing the intermediate fields of UDT/JSONB objects. in that array has a runtime cost of full array data de-serialization every single time. If i perform any UPDATE operation on its elements or add/remove new elements from any position, does PG rewrites the new version of the column value regardless of its size.

Let me know if more inputs are required

--
Thanks,
Piyush Katariya

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux