Re: [HACKERS] constraints in query plans

2006-10-17 Thread Jeff Davis
On Sun, 2006-10-15 at 20:36 -0700, Jeremy Drake wrote: > I just tried that, > CREATE INDEX test_domain_k_x1_x2_mp ON test_domain (k, x1, x2, mp); > > and dropped the others. That actually works properly. > jeremyd=# explain analyze select * from test_domain where k = 1255 and mp; >

Re: [HACKERS] constraints in query plans

2006-10-15 Thread Jeremy Drake
On Sun, 15 Oct 2006, Tom Lane wrote: > Jeremy Drake <[EMAIL PROTECTED]> writes: > > CREATE TABLE test_domain ( > > fkey integer not null, > > kinteger not null, > > x1 integer not null, > > x2 integer, > > mp m_or_p not null > > ); > > > CREATE INDEX test_domain_k_x1_x2_m ON test_do

Re: [HACKERS] constraints in query plans

2006-10-15 Thread Tom Lane
Jeremy Drake <[EMAIL PROTECTED]> writes: > CREATE TABLE test_domain ( > fkey integer not null, > kinteger not null, > x1 integer not null, > x2 integer, > mp m_or_p not null > ); > CREATE INDEX test_domain_k_x1_x2_m ON test_domain (k, x1, x2) WHERE mp = 'm'; > CREATE INDEX test_doma

[HACKERS] constraints in query plans

2006-10-15 Thread Jeremy Drake
I set up the following experiment: CREATE DOMAIN m_or_p AS "char" CHECK (VALUE = 'm' OR VALUE = 'p'); CREATE TABLE test_domain ( fkey integer not null, kinteger not null, x1 integer not null, x2 integer, mp m_or_p not null ); CREATE INDEX test_domain_k_x1_x2_m ON test_domain (k, x