# Issue with Case Sensitivity and Double Quotes in PostgreSQL Query through Logstash

**URL:** <https://discuss.elastic.co/t/issue-with-case-sensitivity-and-double-quotes-in-postgresql-query-through-logstash/355990>\
**Category:** Logstash\
**Created:** [March 22, 2024, 1:51pm UTC](https://discuss.elastic.co/t/issue-with-case-sensitivity-and-double-quotes-in-postgresql-query-through-logstash/355990 "2024-03-22T13:51:31Z")\
**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:** [March 22, 2024, 4:57pm UTC](https://discuss.elastic.co/t/issue-with-case-sensitivity-and-double-quotes-in-postgresql-query-through-logstash/355990/2 "2024-03-22T16:57:14Z")

</div>

> [@Atakan](#):
>
> Has anyone encountered a similar issue

See [this](https://discuss.elastic.co/t/logstash-jdbc-output-to-postgres-case-sensitive-issue/351881) thread. I realize you may not have control of it, but mixed case names in Postgres are a [terrible idea](https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_upper_case_table_or_column_names). Your query contains both single and double quotes, so depending on whether you surround the entire query with single or double quotes you will need to escape the other type of quotes in a way that both logstash and the JDBC code un-escapes them to the right level. I have no idea how to do that.

If SQL allows double quotes around the 2024-03-05 it might be easier.

---

_[View the full topic](https://discuss.elastic.co/t/issue-with-case-sensitivity-and-double-quotes-in-postgresql-query-through-logstash/355990)._