| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andy Colson <andy(at)squeakycode(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unlogged tables |
| Date: | 2010-12-07 22:31:34 |
| Message-ID: | 29798.1291761094@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Dec 7, 2010 at 3:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think a more relevant question is how complicated it'll be to issue
>> those fsyncs --- do you have a concrete implementation in mind?
> It can reuse most of the infrastructure we use for re-initializing
> everything after a crash or unclean shutdown. We just iterate over
> every tablepace/dbspace directory and look for files with _init forks.
> If we find any then we open the main fork files and fsync() each one.
I assume you meant "all the other fork files", but OK. Still, couldn't
that be rather expensive in a large DB?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-12-07 22:43:29 | Re: Final(?) proposal for wal_sync_method changes |
| Previous Message | Tom Lane | 2010-12-07 22:28:25 | Re: Final(?) proposal for wal_sync_method changes |