Table Physical Size Surge

Поиск
Список
Период
Сортировка
От Ashish Kumar Singh
Тема Table Physical Size Surge
Дата
Msg-id CALaESzLD8C-K8c51r5z20iZhONY=TDj8AJ-du9yeOet-jdAwgg@mail.gmail.com
обсуждение исходный текст
Ответы Re: Table Physical Size Surge  (Daniel Gustafsson <daniel@yesql.se>)
Список pgsql-bugs
I have a table :

create table planner.unit_flow_section
(
id
serial,
title
text,
items jsonb[]

);
There is an operation to remove a jsonb element from the items array.
I have an operation which takes a lot of time.
UPDATE planner.unit_flow_section SET items = array_remove(items, '{"a":"b"}'::JSONB) where id = 34;
Few days back we encountered a surge in Database size and within an hour 10GB of data was used up.
After debugging we found this table size increased upto 12GB. We executed this query to get the table size.
SELECT pg_size_pretty( pg_total_relation_size('planner.unit_flow_section') );
But when I create a copy of the table then that table size was only 66MB.
We are using this version of Postgresql:
PostgreSQL 10.6 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11), 64-bit
We are not able to figure out the reason of this.



--
* * * * * * * * * * * * * * * * * * * * * * *
*Thanking You and Regards         *
*Ashish Kumar Singh                *
* * * * * * * * * * * * * * * * * * * * * * * 

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Fan Liu
Дата:
Сообщение: RE: [Bus error] huge_pages default value (try) not fall back
Следующее
От: Daniel Gustafsson
Дата:
Сообщение: Re: Table Physical Size Surge