> 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.
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Andreas Kretschmer
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Alban Hertroys
- Re: *Regarding brin_index on ... Andreas Kretschmer
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on ... Andreas Kretschmer
- Re: *Regarding brin_index on ... Ravi Krishna
- New behavior with JDBC 42.2.5 Ravi Krishna
- Re: New behavior with JDBC 42... Ravi Krishna
- Re: New behavior with JDBC 42... Adrian Klaver
- Re: New behavior with JDBC 42... Ravi Krishna
- Re: New behavior with JDBC 42... Adrian Klaver
- Re: *Regarding brin_index on ... Alban Hertroys
- Re: *Regarding brin_index on ... Durgamahesh Manne
- Re: *Regarding brin_index on required column of the tab... Durgamahesh Manne