Re: Are large objects well supported? Are they considered very stableto use?
От | Chris Bitmead |
---|---|
Тема | Re: Are large objects well supported? Are they considered very stableto use? |
Дата | |
Msg-id | 37000D4A.A7F9351B@bigfoot.com обсуждение исходный текст |
Ответ на | Large objects error - expected a 'V' from the backend (Chris Bitmead <chris.bitmead@bigfoot.com>) |
Ответы |
Re: [HACKERS] Re: Are large objects well supported? Are they considered very stableto use?
|
Список | pgsql-hackers |
> I have tried to use the lo interface and it appears to > work ok (although there is a fix required for solaris). > There is also a memory leak in the back end so several > thousand large objects will probably cause the backend > to fail . Ouch. Well perhaps if I tell you PG hackers what I want to do, if you could tell me the best way to do it. I want to have a comment database storying ascii text comments. These could be over 8000 bytes, and my understanding is that conventional PG rows can't be bigger than 8000 bytes. On the other hand most of them will probably be much smaller than 8000 bytes. I will certainly have more than "several thousand" of them. Is large objects the right way to go here? What are the disk usage / speed tradeoffs of using large objects here, perhaps compared to straight UNIX files? The main reasons I don't use the file system is that I might run out of inodes, and also it's probably not that fast or efficient.
В списке pgsql-hackers по дате отправления: