Thanks Tom,David and Chris for detailed opinions
Regards,
Arun
On Sat, 23 Mar 2024 at 09:25, arun chirappurath
wrote:
> Hi All,
>
> I have a table named users with index on user name.
>
> CREATE TABLE users (
> user_id SERIAL PRIMARY KEY,
> username VARCHAR(50) NOT NULL,
> email VA
arun chirappurath writes:
> I have a table named users with index on user name.
> ...
> When I try to do below select query it's taking seq scan and query returns
> in 5ms.
5ms is an okay runtime, I would think. Is the table empty?
> I am trying to force query to use indexes using query hints
On Fri, Mar 22, 2024 at 8:55 PM arun chirappurath
wrote:
>
> I am trying to force query to use indexes using query hints.
>
> Set enable indexscan to ON,
> Same for bitmap and index only scan
>
Everything is on by default in the planner. You need to think in terms of
what you don't want to hap
> On Mar 22, 2024, at 20:55, arun chirappurath wrote:
> I am trying to force query to use indexes using query hints.
PostgreSQL does not have query hints. Enabling index scans using parameters
doesn't *disable* other types of query nodes.
You can disable sequential scans using:
SE
Hi All,
I have a table named users with index on user name.
CREATE TABLE users (
user_id SERIAL PRIMARY KEY,
username VARCHAR(50) NOT NULL,
email VARCHAR(100) UNIQUE NOT NULL,
age INT
);
CREATE INDEX idx_username ON users (username);
When I try to do below select query it's tak
