Re: Tuple concurrency issue in large objects - Mailing list pgsql-general

From Tom Lane
Subject Re: Tuple concurrency issue in large objects
Date
Msg-id 5126.1576685560@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tuple concurrency issue in large objects  (Justin <zzzzz.graf@gmail.com>)
Responses Re: Tuple concurrency issue in large objects
List pgsql-general
Justin <zzzzz.graf@gmail.com> writes:
> I have a question reading through this email chain.   Does Large Objects
> table using these functions work like normal MVCC where there can be two
> versions of a large object in pg_largeobject .

Yes, otherwise you could never roll back a transaction that'd modified
a large object.

> My gut says no as
> moving/copying potentially 4 TB of data would kill any IO.

Well, it's done on a per-chunk basis (normally about 2K per chunk),
so you won't do that much I/O unless you're changing all of a 4TB
object.

            regards, tom lane



pgsql-general by date:

Previous
From: Justin
Date:
Subject: Re: Tuple concurrency issue in large objects
Next
From: Justin
Date:
Subject: Re: Tuple concurrency issue in large objects