On Thu, 20 May 2004, Bruno Wolff III wrote:
> On Wed, May 19, 2004 at 15:17:01 +0200,
> Atesz <[EMAIL PROTECTED]> wrote:
> >
> > I'd like to ask why the index scaning can't move on an index in
> > multi-order directions (For exapmle: 1.column: forward, 2.column:
> > backward and 3.column: forwa
On Wed, May 19, 2004 at 15:17:01 +0200,
Atesz <[EMAIL PROTECTED]> wrote:
>
> I'd like to ask why the index scaning can't move on an index in
> multi-order directions (For exapmle: 1.column: forward, 2.column:
> backward and 3.column: forward again)? So I wouldn't have to use so many
> indexes. H
Hi all!
Earlier I sent a question about multi-order index scanning
(http://archives.postgresql.org/pgsql-sql/2004-04/msg00276.php).
I can solve the problem with own OPERATOR CLASSes. But this solution
increase number of my indexes exponentially. In my applicaton I have
already more then 200 indexe
