# העברת מסד נתונים נתקעת על ערך עצום של פריט "calendar-details" בטבלה "post\_custom\_fields"

**URL:** <https://meta.discourse.org/t/database-migration-chokes-on-huge-value-of-a-calendar-details-item-in-table-post-custom-fields/172483>\
**Category:** Bug\
**Created:** [7 בדצמבר,‏ 2020,‏ 11:54am UTC](https://meta.discourse.org/t/database-migration-chokes-on-huge-value-of-a-calendar-details-item-in-table-post-custom-fields/172483 "2020-12-07T11:54:54Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [7 בדצמבר,‏ 2020,‏ 3:42pm UTC](https://meta.discourse.org/t/database-migration-chokes-on-huge-value-of-a-calendar-details-item-in-table-post-custom-fields/172483/11 "2020-12-07T15:42:48Z")

</div>

> [@amotl](#):
>
> I already did so. However, the migration process is running into the same situation.

Well, so that means it has nothing to do with the PG12 update, so not my fault 😛

> [@amotl](#):
>
> So, the `value` column of this specific `calendar-details` item contains ~80MB worth of data. I believe we are on to something here.

Yeah, as we said several times using either plugin store or post\_custom\_fields for stuff that is complex is not sustainable long term. That is why calendar is doing [this migration](https://github.com/discourse/discourse-calendar/blob/master/db/migrate/20200226183018_create_calendar_events.rb) to move to proper tables.

Unfortunately looks like it didn’t come early enough for you and a event got in a bad state. Delete the problematic row and stuff should work again.

---

_[View the full topic](https://meta.discourse.org/t/database-migration-chokes-on-huge-value-of-a-calendar-details-item-in-table-post-custom-fields/172483)._
