| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Large object + FREEZE? |
| Date: | 2013-07-02 14:36:34 |
| Message-ID: | 20130702143634.GA5361@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 2, 2013 at 12:16:18PM +0900, Tatsuo Ishii 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.
I was not aware that large objects had to feeze each 8k segment. Do
they?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-07-02 14:38:17 | Re: MVCC catalog access |
| Previous Message | Fabrízio de Royes Mello | 2013-07-02 14:32:37 | Re: Add regression tests for DISCARD |