Re: *Regarding brin_index on required column of the table

From: "Ravi Krishna" <srkrishna(at)usa(dot)com>
To: "Andreas Kretschmer" <andreas(at)a-kretschmer(dot)de>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: *Regarding brin_index on required column of the table
Date: 2018-09-21 16:47:28
Message-ID: trinity-e205320a-5b71-4d9b-88d7-950334eeddb7-1537548448236@3c-app-mailcom-lxa12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> i can see a lot of max(string-field) (for instance, LastName,
> MiddleName, FirstName).
> wild guess: completely broken design, but i don't know your application
> and use-case for that.
> again, as i said already, i think this is a case for an in-deep
> consultation.

My thoughts exactly. There is a UNION also.
A mere look at the SQL indicates that it will be a miracle if this runs fast. Tuning such queries
in a mailing list is difficult, the best we can do is to give suggestion.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ravi Krishna 2018-09-21 17:12:04 New behavior with JDBC 42.2.5
Previous Message Andreas Kretschmer 2018-09-21 16:32:06 Re: *Regarding brin_index on required column of the table