Re: SUBSTRING performance for large BYTEA

"Karsten Hilbert" <Karsten.Hilbert@gmx.net> writes:

> But maybe this can be nefariously interpreted such that I could sort-of
> implement cutoff-based extended/external switching by prepending "alter
> table ... set storage external/extended ..." to INSERTs/UPDATEs based on
> bytea parameter size. Or even writing a trigger issuing ALTER TABLE
> depending on size of insert ?

I wouldn't suggest doing that. It will bloat the pg_attribute catalog table
and require a lot of extra vacuums. I think it would also create some lock
contention issues.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com