| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> | 
|---|---|
| To: | robertmhaas(at)gmail(dot)com | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Large object + FREEZE? | 
| Date: | 2013-07-02 16:29:40 | 
| Message-ID: | 20130703.012940.1142100617623302179.t-ishii@sraoss.co.jp | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
> On Mon, Jul 1, 2013 at 11:16 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> Now that we have COPY FREEZE, I'm thinking about adding similar option
>> to creating large objects. In 9.3 the maximum size of large objects
>> are increased. That means, the first access to a large object will
>> trigger more writes because of hint bit updation. Also subsequent
>> VACUUM may trigger that as well. If we could freeze arge objects while
>> creating, it could reduce the writes dramatically as COPY FREEZE
>> already does.
>>
>> Opinions?
> 
> COPY FREEZE only works if the table was created in the same
> transaction.  Otherwise, an error midway through could leave the table
> and index inconsistent.  I think that's a killer for this proposal,
> because obviously when a large object is created, pg_largeobject will
> be pre-existing.
Argh. You are right.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-02 16:41:21 | Re: LATERAL quals revisited | 
| Previous Message | David Fetter | 2013-07-02 16:12:11 | Re: Custom gucs visibility |