Yes, you can use a hideous non-scalable query segment along the lines of:
where upper(name) like 'MARIA % GARRALON'
or you can do it the right way :-)
Introduce another column like first_and_last_name
and use an insert/update trigger to populate it with the correct value maria garralon
. Then index that column and your queries will be the blindingly fast:
where first_and_last_name = 'maria garralon'
That moves the cost of calculation to the insert/update where it belongs, rather than the select where the cost is incurred unnecessarily. The data only changes on insert/update so that's the only time you should need to incur that cost.
If your needs are more complicated than a simple first and last name, you can populate other tables in your triggers.