Re: 8K Limit, whats the best strategy?
От | Poul L. Christiansen |
---|---|
Тема | Re: 8K Limit, whats the best strategy? |
Дата | |
Msg-id | 39A148B7.7D67B0BD@faroenet.fo обсуждение исходный текст |
Ответ на | 8K Limit, whats the best strategy? (Keith Wong <keith@e-magine.com.au>) |
Ответы |
Re: 8K Limit, whats the best strategy?
|
Список | pgsql-sql |
Jan Wieck wrote: > Poul L. Christiansen wrote: > > I've just split the text up (in 8 pieces), so it fits into 8K rows. But thats > > only a viable solution if your text is less than a couple of 100K's. > > > > You could try to be a daredevil and use the Toast code, even if it's beta. But > > I don't know how far the Toast project has come. > > TOAST is finished and will be shipped with 7.1. It's not a > solution for huge items, but medium sized text up to some > hundred K works fine. What do you mean by "..not a solution for huge items"? Does TOAST have a size limit? > > > Jan > > > > > Keith Wong wrote: > > > > > Hi everyone, > > > > > > Just wondering what strategies people have used to get around the 8K row > > > limit in Postgres. > > > If anyone has been troubled by this limitation before and has a nice > > > solution around it, I would love to hear it. > > > > > > My application is a web-based system in which needs to store large amounts > > > of text. > > > The text stored needs to searchable as well. > > > > > > Cheers, > > > Keith. > > > > -- > > #======================================================================# > # It's easier to get forgiveness for being wrong than for being right. # > # Let's break this rule - forgive me. # > #================================================== JanWieck@Yahoo.com #
В списке pgsql-sql по дате отправления: