agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: Paul M. Aoki <aoki@CS.Berkeley.EDU>
To: Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>
Cc: Postgres Mailing List <postgres@postgres.Berkeley.EDU>
Subject: Re: New type and pg_operator.
Date: Fri, 15 Jul 94 05:34:41 -0700
Message-ID: <199407151234.FAA25331@nobozo.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.3.89.9407151351.C21375-0100000@ccfs1>

the info needed to add new operators and stuff is in chapter 13 of
the user manual.

Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl> writes:
> surprising for me that for all operators connected with char/text types
> field oprprec (operator precedence) is equal 0. Why ?

doesn't work anyway.

>  Does exist some (simple :-) explanation what join strategies mean ?

sure, in any database textbook..

the nickle version:

nestloop join - compare everything in A to everything in B

sortmerge join - exploit sorted order to avoid scanning things in 
B known not to match the current element of A (too big, too small,
whatever).

hash join - join only those elements that fall into the same hash 
bucket (same idea - if it doesn't hash into the same bucket, it's 
not bitwise equal, so you don't have to look at it)

> And why hash join strategy is defined (oprcanhash = t) just for "=" ?

unless you use arcane order-preserving hash functions, hash join 
only makes sense for bitwise equality.

> And why
> merge-sort join strategy is not defined for all char/text operators ie. 
> oprrsortop and oprlsort are equal to 0 ?

i have no idea why not.
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================

reply

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: postgres@postgres.berkeley.edu
  Cc: aoki@CS.Berkeley.EDU, Wojtek.Bogusz@fuw.edu.pl
  Subject: Re: New type and pg_operator.
  In-Reply-To: <199407151234.FAA25331@nobozo.CS.Berkeley.EDU>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox