Re: Storing images as BYTEA or large objects - Mailing list pgsql-general

From Adam Rich
Subject Re: Storing images as BYTEA or large objects
Date
Msg-id 037b01c86df6$04a6ecd0$0df4c670$@r@sbcglobal.net
Whole thread Raw
In response to Re: Storing images as BYTEA or large objects  (Andy Colson <andy@squeakycode.net>)
Responses Re: Storing images as BYTEA or large objects
List 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)







pgsql-general by date:

Previous
From: Ken Johanson
Date:
Subject: Re: SELECT CAST(123 AS char) -> 1
Next
From: "Dean Gibson (DB Administrator)"
Date:
Subject: Re: SELECT CAST(123 AS char) -> 1