# Database migratie hapert op enorme waarde van een "calendar-details" item in tabel "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 december 2020 om 11:54 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:** 9

<div class="post-metadata">

### Author: ![amotl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amotl/32/109873_2.png) [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [7 december 2020 om 14:49 UTC](https://meta.discourse.org/t/database-migration-chokes-on-huge-value-of-a-calendar-details-item-in-table-post-custom-fields/172483/9 "2020-12-07T14:49:38Z")

</div>

> [@amotl](#):
>
> However, as soon as I select the `value` column, all things go south.

Ha. Is this sane?

```plaintext
DB.query_single('SELECT name, length(value) FROM "post_custom_fields" WHERE post_id=20')
=> ["calendar-details", 83361791, "post_detected_lang", 2]

```

So, the `value` column of this specific `calendar-details` item contains ~80MB worth of data. I believe we are on to something here.

Apparently, this is the only item carrying such a large payload within its `calendar-details` value.

```plaintext
print(DB.query("SELECT post_id, length(value) FROM post_custom_fields WHERE name='calendar-details' ORDER BY post_id").map { |r| r.post_id.to_s + ": " + r.length.to_s }.join("\n"))
20: 83361791
84: 113
133: 113
177: 58
223: 2
263: 113
379: 112
385: 130
439: 112
456: 112
457: 58
495: 117
552: 2

```

---

_[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)._