# Parsing postgresql logs

**URL:** <https://discuss.elastic.co/t/parsing-postgresql-logs/220017>\
**Category:** Logstash\
**Created:** [February 19, 2020, 4:05pm UTC](https://discuss.elastic.co/t/parsing-postgresql-logs/220017 "2020-02-19T16:05:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manoj\_kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manoj_kumar4/32/45160_2.png) [@Manoj\_kumar4](https://discuss.elastic.co/u/Manoj_kumar4)\
**Post date:** [February 19, 2020, 4:05pm UTC](https://discuss.elastic.co/t/parsing-postgresql-logs/220017/1 "2020-02-19T16:05:28Z")

</div>

Hi friends,

Can you share grok pattern for Postgres logs (9.6+ version)

```auto
2020-02-18 12:33:21 UTC:10.32.75.210(32848):user@servicedb:[24531]:WARNING: there is no transaction in progress

```

---

<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:** [February 19, 2020, 7:09pm UTC](https://discuss.elastic.co/t/parsing-postgresql-logs/220017/2 "2020-02-19T19:09:59Z")

</div>

For a log message like that I would use dissect rather than grok.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 18, 2020, 7:10pm UTC](https://discuss.elastic.co/t/parsing-postgresql-logs/220017/3 "2020-03-18T19:10:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.