Re: [PERFORM] forced sequential scan when condition has current_user

2010-01-05 Thread Keresztury Balázs
3:16 PM To: 'Keresztury Balázs'; pgsql-performance@postgresql.org Subject: RE: [PERFORM] forced sequential scan when condition has current_user > -Mensaje original- > De: Keresztury Balázs > > hi, > > just a small question: is it normal that PostgreSQL 8.4

Re: [PERFORM] forced sequential scan when condition has current_user

2010-01-04 Thread Keresztury Balázs
you think this is actually a bug, not a feature? balazs -Original Message- From: Robert Haas [mailto:robertmh...@gmail.com] Sent: Monday, January 04, 2010 10:59 PM To: Keresztury Balázs Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] forced sequential scan when condition has curr

[PERFORM] forced sequential scan when condition has current_user

2010-01-04 Thread Keresztury Balázs
hi, just a small question: is it normal that PostgreSQL 8.4.1 always uses sequential scanning on any table when there is a condition having the constant "current_user"? Of course there is a btree index set on that table, but the DBMS just doesn't want to utilize it. When I replace current_user to