| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Glen and Rosanne Eustace <agree(at)godzone(dot)net(dot)nz> |
| Cc: | pgsql-general <pgsql-general(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] Keyed Tables |
| Date: | 1999-05-23 06:32:45 |
| Message-ID: | 199905230632.CAA23239@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> I thought I had already posted this query but now I can't remember. If
> I have please excuse the repeat. But as I can't remember the answer
> either can someone please comment.
>
> Is there likely to be any attempt to allow a table to be keyed. It
> seems that by default a table is created as a heap and in order to
> improve access speed, one must create indices on that table.
>
> I use Ingres at work and quite like the ability to do a 'modify table to
> btree' type of command. When the table concerned is basically only a
> key plus value, it seems rather inefficient to have to have both the
> heap and then an index when supposedly one could simply make the table
> into a btree in the first place.
Yes, it is a nice feature, but we don't support it. We do have CLUSTER,
but that is not as nice.
--
Bruce Momjian | http://www.op.net/~candle
maillist(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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-05-23 06:33:17 | Re: [GENERAL] Compile problem on BSDi 3.0 |
| Previous Message | Gary Hoffman | 1999-05-23 05:48:02 | Compile problem on BSDi 3.0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 1999-05-23 07:35:09 | Re: [HACKERS] strange behavior of UPDATE |
| Previous Message | Vadim Mikheev | 1999-05-23 05:51:50 | Re: [HACKERS] Current TODO list |