Re: Performance (was: The New Slashdot Setup (includes MySql server))

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance (was: The New Slashdot Setup (includes MySql server))
Date: 2000-05-20 01:46:43
Message-ID: 200005200146.VAA25437@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> I wrote:
> > We should just need a switching layer in front of heap_beginscan/
> > index_beginscan and heap_getnext/index_getnext...)
>
> After refreshing my memory of how these are used, it seems that
> we'd have to change the API of either the heap or index scan routines
> in order to unify them like that. Might be worth doing to maintain
> code cleanliness, though. The places Hiroshi has fixed to support
> both index and seq scan look really ugly to my eyes ...

Agreed, and I think there are a few places that have them.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Lockhart 2000-05-20 01:53:28 Re: Performance (was: The New Slashdot Setup (includes MySql server))
Previous Message Paul Dlug 2000-05-20 01:31:33 Re: Zip Code Proximity

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2000-05-20 01:53:28 Re: Performance (was: The New Slashdot Setup (includes MySql server))
Previous Message Tom Lane 2000-05-20 00:32:18 Re: Performance (was: The New Slashdot Setup (includes MySql server))