Re: PHP-Postgres, using large objects
| From: | Jouni Ahto | Date: | Fri, 07 Jul 2000 23:05:15 +0000 |
| Subject: | Re: PHP-Postgres, using large objects | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-965@lists.php.net to get a copy of this message | ||
On Fri, 7 Jul 2000, Hanson, Donna wrote:
> Hi,
> Does anyone have experience with large objects? I need to display news
> articles on an archive web page and want to use this feature with
> php/postgres, I'm wondering if it works and what initial considerations I
> should know about.
Large objects works but I wouldn't recommend them for your kind of use.
They use disk space *very* ineffectively and about the only thing you can
do to them is either read or write. Their primary use is in special
applications where someone writes additional functions in C to be loaded
into PostgreSQL, so you can do queries based on their contents.
Use text as the type for your news articles. As a note, out of box
PostgreSQL limits the amount of data that one row in a table can have to
approximately 8k. If you need more, you must recompile PostgreSQL after
raising the value of MAXBLCKSZ include/storage/bufmgr.h in PostgreSQL main
src directory. Possible values are 16384 and 32768, you can't get more.
(Hmm, just checked, it is already the max value in 7.0.2. They have
suspected more in 7.1 or 7.2 series.)
-- Jouni Ahto