| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | t-ishii(at)sra(dot)co(dot)jp |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Arbitrary tuple size |
| Date: | 1999-07-09 05:29:18 |
| Message-ID: | 199907090529.BAA10736@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >If we get wide tuples, we could just throw all large objects into one
> >table, and have an on it. We can then vacuum it to compact space, etc.
>
> I thought about that too. But if a table contains lots of LOs,
> scanning of it will take for a long time. On the otherhand, if LOs are
> stored outside the table, scanning time will be shorter as long as we
> don't need to read the content of each LO type field.
Use an index to get to the LO's in the table.
--
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-07-09 05:29:46 | Re: [HACKERS] Arbitrary tuple size |
| Previous Message | Vadim Mikheev | 1999-07-09 05:27:55 | Re: [HACKERS] Arbitrary tuple size |