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: | Mateus Cordeiro Inssa <mateus(at)ifnet(dot)com(dot)br>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Error "vacuum pg_proc" |
Date: | 1999-12-27 02:19:48 |
Message-ID: | 199912270219.VAA27313@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I spent some more time looking into this, and found out that actually
> the safe upper limit for btree index entries is not ~ BLCKSZ/2, but
> ~ BLCKSZ/3. btree needs to be able to insert two items on every page,
> but it *also* keeps an extra item (the "high key") on non-rightmost
> pages. So if any item exceeds one-third the available space, you run
> a risk of failure depending on what page it ends up on and what else
> is on that same page.
>
> It turns out that for an index on a single text column, the maximum
> safe text length is 2700 bytes. So the correct check for dangerous
> procedure definitions in 6.5.* is
This is another argument to try and get long tuples into 7.0.
--
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 03:22:56 | Re: [HACKERS] Error "vacuum pg_proc" |
Previous Message | Ryan Kirkpatrick | 1999-12-27 01:05:02 | Re: [HACKERS] database replication |