Bruce Toback wrote:
> The key limitations of PostgreSQL are:
>
> - A maximum tuple size of 8192 bytes in the default build, and 32768
>   bytes no matter what. There are performance reasons for not just
>   choosing the maximum as the default. This limit ought to be familiar to
>   IMAGE users; we can only have 4096-byte tuples, and we can't even
>   trade off performance to get more.
>
>   The PostgreSQL developers are working to remove the limitation, which
>   dates back to the database system's earliest days. This is an advantage
>   to open source: if the itch is bad enough, you can scratch it. In
>   addition, there's also BLOB support, which helps a lot in ameliorating
>   the tuple size limitation. Again, open source made it possible to
> scratch
>   an itch.
>
> - No outer joins. These can be simulated with a UNION, so it's no big
> deal.

Both of these limitations no longer apply in what will be released as
PostgreSQL 7.1:

http://postgresql.readysetnet.com/devel-corner/docs/postgres/release.html
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...