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: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Error "vacuum pg_proc" |
Date: | 1999-12-27 03:36:19 |
Message-ID: | 199912270336.WAA28667@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> It turns out that for an index on a single text column, the maximum
> >> safe text length is 2700 bytes.
>
> > This is another argument to try and get long tuples into 7.0.
>
> I think Jan might have enough on his plate already without trying to
> TOAST the index code along with the plain-table code. But if he can
> get it done, great!
>
> One thing this does bring up is that the maximum safe tuple length is
> dependent on the index or table type. The toaster's API had better
> be designed accordingly...
In talking to Jan, the index code will make use of the toast entries
automatically. He said the heap_insert will do any toasting, and after
that the tuple already has any toast pointers, and that gets inserted
into the index.
--
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 | Tom Lane | 1999-12-27 04:14:25 | Re: [HACKERS] Error "vacuum pg_proc" |
Previous Message | Tom Lane | 1999-12-27 03:22:56 | Re: [HACKERS] Error "vacuum pg_proc" |