Re: SUBSTRING performance for large BYTEA

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: SUBSTRING performance for large BYTEA
Date: 2007-08-18 23:07:46
Message-ID: 87ir7csapp.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


"Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Phoenix Kiula 2007-08-19 02:10:37 Re: Automating logins for mundane chores
Previous Message dustov 2007-08-18 22:21:02 PGError: input out of range