UdmSearch: tables vs indices ...

We've almost got UdmSearch up and running, and I'm noticing something odd:

-rw------- 1 pgsql pgsql 204800 Jan 6 00:05 url
-rw------- 1 pgsql pgsql 1622016 Jan 6 00:05 word_url

url is:

CREATE TABLE "url" (
"rec_id" int4 DEFAULT nextval('next_url_id') PRIMARY KEY,
"status" int4 NOT NULL DEFAULT 0,
"url" character varying(128) NOT NULL,
"content_type" character varying(32) NOT NULL DEFAULT '',
"last_modified" character varying(32) NOT NULL DEFAULT '',
"title" character varying(128) NOT NULL DEFAULT '',
"text" character varying(255) NOT NULL DEFAULT '',
"size" int4 NOT NULL DEFAULT 0,
"indexed" int4 NOT NULL DEFAULT 0,
"last_index_time" datetime NOT NULL DEFAULT 'Thu Dec 31 20:00:00 1970 GMT',
"next_index_time" datetime NOT NULL DEFAULT 'Thu Dec 31 20:00:00 1970 GMT',
"referrer" int4 NOT NULL DEFAULT 0,
"tag" int4 NOT NULL DEFAULT 0,
"hops" int4 NOT NULL DEFAULT 0,
"keywords" character varying(255) NOT NULL DEFAULT '',
"description" character varying(100) NOT NULL DEFAULT '',
"crc" character varying(33) NOT NULL DEFAULT '');

and word_url is:

CREATE INDEX "word_url" on "dict" using btree ( "word" "varchar_ops", "url_id" "int4_ops" );

=============

is it just me, or does an index ~6x the size of the data itself look
"odd"?

Its an older v6.5.0 database (haven't had time to upgrade *sigh*), so if
explains it, so be it...I'll do an upgrade ASAP...but if that doesn't?

Thanks...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org