| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: random access - bytea |
| Date: | 2003-10-26 15:04:46 |
| Message-ID: | Pine.LNX.4.44.0310261602000.3817-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 26 Oct 2003, Hannu Krosing wrote:
> I brought it up once and Tom answered that TOAST tables are not
> transaction aware, so you can't update just some parts of toasted
> entities - you must always write the whole fields. So this will not be
> just an api change.
Yes, the blocks (or what one selects to work with) in a toasted field have
to have transaction stuff stored, just like tuples. That is clear if
different transactions shall have different views of the "file".
--
/Dennis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Witney | 2003-10-26 15:16:54 | Re: shared memory on OS X - 7.4beta4 |
| Previous Message | Hannu Krosing | 2003-10-26 14:56:12 | Re: random access - bytea |