Skip site navigation (1) Skip section navigation (2)

Re: index support is NULL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: index support is NULL
Date: 2007-04-03 01:16:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Your patch has been added to the PostgreSQL unapplied patches list at:

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.


Teodor Sigaev wrote:
> Initially patch was developed by Martijn van Oosterhout. But it's reworked  and 
> support of searching NULLS to GiST too. Patch adds new column named amsearchnull 
> to pg_am. To recognize IS NULL clause ScanKey->sk_flags contains (SK_ISNULL & 
> SK_INDEXFINDNULL) and ScanKey->sk_strategy sets to InvalidStrategy. IS NOT NULL 
> isn't supported.
> The patch was already suggested to community 
> (
> and, but the 
> single objection was:
> Objection was about representing IS [NOT] NULL clause in SkanKey structure, 
> because it required to set strategy to BTEqualStrategyNumber, and Tom doubted 
> about needing of such support.
> Now ScanKey->sk_strategy = InvalidStrategy and btree code transforms it to 
> BTEqualStrategyNumber in _bt_preprocess_keys(), btcostestimate knows that fact too.
> GiST doesn't need to transform strategy - it looks at SK_INDEXFINDNULL only.
> -- 
> Teodor Sigaev                                   E-mail: teodor(at)sigaev(dot)ru
>                                                     WWW:
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-04-03 01:23:05
Subject: Re: Add usage counts to pg_buffercache
Previous:From: Bruce MomjianDate: 2007-04-03 01:09:15
Subject: Re: Make CLUSTER MVCC-safe

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group