Metabase select not finding correct data

I can't say this is a bug or not, Im selecting a certain data in my metabase but it doesnt find the correct column, but I use the same select (same db, same user), on dbeaver, and it works ...
The field is a varchar(150), when using "ilike" instead of "=" works, but ilike performace is not ideal.

Hi @reddy

With so little information, I would say that the problem is elsewhere.

Post "Diagnostic Info" from Admin > Troubleshooting.

And provide a more detailed description of the problem.

Sorry, I edited the question. I sent it without finishing the text.

@reddy Post "Diagnostic Info" from Admin > Troubleshooting. If you are getting values, when you use ilike, then you might have spaces or some other character problem.

"browser-info": {
"language": "en-US",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.87 Safari/537.36",
"vendor": "Google Inc."
"system-info": {
"file.encoding": "UTF-8",
"": "OpenJDK Runtime Environment",
"java.runtime.version": "1.8.0_282-b08",
"java.vendor": "OpenJDK BSD Porting Team",
"java.vendor.url": "",
"java.version": "1.8.0_282",
"": "OpenJDK 64-Bit Server VM",
"java.vm.version": "25.282-b08",
"": "FreeBSD",
"os.version": "13.0-RELEASE",
"user.language": "en",
"user.timezone": "America/Sao_Paulo"
"metabase-info": {
"databases": [
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "13.2"
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.23"
"run-mode": "prod",
"version": {
"tag": "v0.41.3.1",
"date": "2021-12-02",
"branch": "release-x.41.x",
"hash": "20f9097"
"settings": {
"report-timezone": "America/Buenos_Aires"

Could it be space issue, even when using the same query on dbeaver works?
Are there any difference on how metabase uses varchar fields?

@reddy You should upgrade immediately to a newer release:

And you might want to upgrade Java too:

Metabase sends the query to your database, so check your database query log and compare it with what DBeaver is sending. Both are just clients that sends queries, the only different is the driver/version that it's using.

Ok thank you, once I get access to the logs i'll update this thread with both queries.

It was a postgres index error, caused by a new version of postgres, not related to Metabase.

1 Like