# Possible issue with tracking\_column\_type =\> "timestamp" in 8.1.1

**URL:** <https://discuss.elastic.co/t/possible-issue-with-tracking-column-type-timestamp-in-8-1-1/336255>\
**Category:** Logstash\
**Created:** [June 16, 2023, 6:56pm UTC](https://discuss.elastic.co/t/possible-issue-with-tracking-column-type-timestamp-in-8-1-1/336255 "2023-06-16T18:56:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [June 16, 2023, 8:18pm UTC](https://discuss.elastic.co/t/possible-issue-with-tracking-column-type-timestamp-in-8-1-1/336255/2 "2023-06-16T20:18:17Z")

</div>

I think that [this](https://github.com/logstash-plugins/logstash-integration-jdbc/commit/c06e3192d8da3528bf4fc045b3fd8721b60a5a1e) PR (committed yesterday) is intended to fix that. Specifically "Ruby 3.1 comes with Psych 4 which switched the alias of load from unsafe\_load to safe\_load".

---

_[View the full topic](https://discuss.elastic.co/t/possible-issue-with-tracking-column-type-timestamp-in-8-1-1/336255)._