| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CLOG extension |
| Date: | 2012-05-03 19:18:45 |
| Message-ID: | CA+TgmobS+PzLa+oq3simwakSeJJxtH3Nerh-RdViy0qcgrdHaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 3, 2012 at 2:50 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Doing it a background process, though, may make sense. What I'm a
> little worried about is that - on a busy system - we've only got about
> 2 seconds to complete each CLOG extension, and we must do an fsync in
> order to get there.
Scratch that - we don't routinely need to do an fsync, though we can
end up backed up behind one if wal_buffers are full. I'm still more
interested in the do-it-a-page-in-advance idea discussed upthread, but
this might be viable as well.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-05-03 19:20:45 | Re: CLOG extension |
| Previous Message | Josh Berkus | 2012-05-03 19:06:30 | Re: Temporary tables under hot standby |