From: David Hartwig <daveh@insightdist.com>
To: Sferacarta Software <sferac@bo.nettuno.it>
Cc: pgsql-interfaces@postgreSQL.org
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] using indexes with the OR clause
Date: Tue, 20 Oct 1998 11:34:38 -0400
Message-ID: <362CAD8D.EAC7CEE8@insightdist.com> (raw)
References: <11661.981020@bo.nettuno.it>
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'
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: daveh@insightdist.com, sferac@bo.nettuno.it, pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] using indexes with the OR clause
In-Reply-To: <362CAD8D.EAC7CEE8@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox