From: | Denis Perchine <dyp(at)perchine(dot)com> |
---|---|
To: | Chris Bitmead <chris(at)bitmead(dot)com> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Patch for better large objects support |
Date: | 2000-06-13 09:25:37 |
Message-ID: | 00061316281907.00525@dyp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> > > > 2. For really large objects TOAST will be really inefficient for quite small < 64K other
> > > > way around.
> > >
> > > Why will toast be inefficient for really large objects?
> >
> > Because data is stored in relations, and there's extra overhead for managing them.
> > Just look on Jan's mail in [HACKERS] for better description of the difference.
>
> According to Tom's last email, current LOs are stored in relations now.
That was a part of my patch. :-)) Anyway I will try to implement one-table LO storage
for transaction integrity. Read Jan's mail.
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: dyp(at)perchine(dot)com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2000-06-13 09:28:37 | Re: Big 7.1 open items |
Previous Message | Chris Bitmead | 2000-06-13 09:19:07 | Re: Patch for better large objects support |