Re: Storing images as BYTEA or large objects

From: "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Storing images as BYTEA or large objects
Date: 2008-02-13 04:07:58
Message-ID: 037b01c86df6$04a6ecd0$0df4c670$@r@sbcglobal.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > I have two options for storing this data: As BYTEA or as large objects.

Is it true that if you update a row containing a large BYTEA value, (even if
you're not updating the BYTEA field itself, just another field), it requires

the entire BYTEA value to be copied to a new row (because of MVCC) ? Or is
this not true because of TOAST?

If true, would this have an impact on the buffer cache and/or checkpoints ?
(You could always separate out the BYTEA values to their own table by
themselves to avoid this drawback)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2008-02-13 04:34:26 Re: SELECT CAST(123 AS char) -> 1
Previous Message Ken Johanson 2008-02-13 03:39:05 Re: SELECT CAST(123 AS char) -> 1