Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> I'm wondering if TOAST is going to be efficient enough for me to plonk
> multimegabyte email attachments into the database.
Should work. The main limitation on TOAST is that it wants to treat
each datum as a unit, ie you must fetch or store the whole value in one
go. When your datums get big enough that that's inconvenient, you won't
like TOAST so much. I don't foresee it being a big issue for emailable
items though ...
> However I've also a suspicion that there might be problems doing
> INSERT INTO mytable (a) values ( 'aa.......');
> Where aa... is a few megabytes long :). There's probably a query size limit
> somewhere between my app and TOAST.
I've tested this, it works fine since 7.0 or so.
Amusing anecdote: since 7.0, MySQL's "crashme" test crashes when run
against Postgres. Postgres is fine, it's the perl job running the
crashme script that goes belly-up. It seems that crashme's loop that
tries to discover the maximum query length is more memory-hungry than
Postgres itself, and so the perl job hits the kernel-imposed maximum
process size before the backend does. Moral: before assuming Postgres
can't do something, make sure your own code can hold up its end...
regards, tom lane
