How do senior database administrators approach PostgreSQL performance tuning when query execution plans start showing sequential scans on large tables?