Alexaki Sofia <[EMAIL PROTECTED]> writes:
> But as I see from the query plan the indexes are not used, instead
> sequential search is done either I define indexes or not.
> As you can see below the query plan remains the same.
> Is that reasonable??? Shouldn't Postgresql use the indexes in order
"Michael Richards" <[EMAIL PROTECTED]> writes:
> I've got a postgres system that keeps going into recovery mode. I
> can't really find any docs on this. All of the postgres processes
> will be in the STOP state and when I try to connect it will say "The
> database is in recovery mode".
> I sus
I'm doing this:
CREATE TABLE data ( val int4 );
CREATE TABLE pos ( ) INHERITS ( data );
CREATE TABLE neg ( ) INHERITS ( data );
CREATE RULE data_to_pos AS
ON INSERT TO data WHERE NEW.val > 0
DO INSTEAD
INSERT INTO pos ( val ) VALUES ( NEW.val );
CREATE RULE data_to_neg AS
ON
Itai Zukerman <[EMAIL PROTECTED]> writes:
> CREATE RULE data_val AS
> ON SELECT TO data
> DO INSTEAD
> SELECT * FROM pos
> UNION
> SELECT * FROM neg;
IIRC, UNION doesn't work in rules at the moment (a fix is planned for
7.2). But what's the point of splitting the data into the
