Message-Id: <362CAD8D.EAC7CEE8@insightdist.com>
Date: Tue, 20 Oct 1998 11:34:38 -0400
From: David Hartwig <daveh@insightdist.com>
Organization: Insight Distribution Systems
Mime-Version: 1.0
To: Sferacarta Software <sferac@bo.nettuno.it>
Cc: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] using indexes with the OR clause
References: <11661.981020@bo.nettuno.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

In the "Connect Settings" (either global or per data source) add the
following line:
    SET ksqo TO 'on'

Stands for "Key Set Query Oprimizer".    It actually breaked those nasty
OR's into UNIONS.  There will eventually be a radio button for this.
We have be in a crunch lately at work.

Are you using row versioning?  If so, you may have to overload an
operator for > on xid.

Let me know how it goes.


Sferacarta Software wrote:

> Hi all,
>
> I'm trying v6.4beta2 via ODBC-Access.
>
> I have the following table:
>
> CREATE TABLE attivita (
>         azienda                 CHAR(11) NOT NULL,
>         attivita                CHAR(03) NOT NULL,
>         specifica               CHAR(02),
>         cod_alternativo         CHAR(10),
>         conto_economico         CHAR(02),
>         inizio_attivita         DATE,
>         fine_attivita           DATE,
>         PRIMARY KEY (azienda,attivita,specifica,inizio_attivita)
>         );
>
> I linked this table on M$-Access specifying the Access-key equal to
> PostgreSQL PRIMARY KEY to test indexes with the OR clause but
> I have the following error message:
>
> 'FATAL 1: palloc failure memory exhausted'
>
> Any ideas ?
>
> There's the PSLODBC.LOG file attached.
>
> Jose'