I checked all the indexes are defined on the tables however the query seems
slow, below is the plan. Can any one give any pointers to verify ?
SELECT a.menu_item_id, a.menu_item_name, a.menu_item_category_id,
b.menu_item_category_desc, c.menu_item_variant_id,
c.menu_item_variant_type_id, c.price,
> On Jun 8, 2021, at 09:03, Ayub Khan wrote:
> I checked all the indexes are defined on the tables however the query seems
> slow, below is the plan.
It's currently running in slightly under six milliseconds. That seems
reasonably fast given the number of operations required to fulfill it.
In AWS RDS performance insights the client writes is high and the api
which receives data on the mobile side is slow during load test.
On Tue, 8 Jun 2021, 19:03 Ayub Khan, wrote:
>
> I checked all the indexes are defined on the tables however the query
> seems slow, below is the plan. Can any o
Ayub Khan writes:
> I checked all the indexes are defined on the tables however the query seems
> slow, below is the plan. Can any one give any pointers to verify ?
You might try to do something about the poor selectivity estimate here:
> -> Index Scan usin
below is function definition of is_menu_item_available, for each item
based on current day time it returns when it's available or not. The same
api works fine on oracle, I am seeing this slowness after migrating the
queries to postgresql RDS on AWS
CREATE OR REPLACE FUNCTION is_menu_item_availab
