"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> I would like to improve the response time of the following SQL command
Try getting rid of the silly concatenate-with-empty-string operations
that appear to lurk within some view underlying this command. Those
seem to be defeating the planner's abil
Hi,
I would like to improve the response time of the following SQL command but I
need some help to indentify where is it taking most of the processing time.
It seams that it is in the Seq Scan on tt_gra gra, but not sure. Am I right?
Can a new index help in this issue?
Thank you in advance!
e
