newbie question: bytea v. large objects

Hello all,

I've been doing a little bit of reading on the difference between large objects and bytea. Bytea feels a little bit more like what I'm use to with Oracle, MSSQL, etc. However, I'm leaning towards using large objects, but one thing in the documentation is bothering me:

>From documentation:

( http://www.postgresql.org/docs/8.3/interactive/lo-intro.html )

"PostgreSQL also supports a storage system called "TOAST" that automatically stores values larger than a single database page into a secondary storage area per table. This makes the large object facility partially obsolete."

I think it's the word "obsolete" that is bothering me :)

Does anyone know if I should consider large objects to be depreciated, and if there are plans for them to someday go away?

Any other advice on the subject or links to reading I should do will be much appreciated.

Thanks,

David