| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb) |
| Date: | 2010-02-14 17:11:39 |
| Message-ID: | 22295.1266167499@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> So I think we have a bigger problem than just copydir.c. It seems to
> me we should be fsyncing the table space data directories on every
> checkpoint.
Is there any evidence that anyone anywhere has ever lost data because
of a lack of directory fsyncs? I sure don't recall any bug reports
that seem to match that theory.
It seems to me that we're talking about a huge hit in both code
complexity and performance to deal with a problem that doesn't actually
occur in the field; and which furthermore is trivially solved on any
modern filesystem by choosing the right filesystem options. Why don't
we just document those options, instead?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2010-02-14 17:17:42 | Re: function to display ddl |
| Previous Message | Greg Stark | 2010-02-14 17:06:09 | Re: Optimizing GetConflictingVirtualXIDs() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arjen van der Meijden | 2010-02-14 17:12:00 | Re: PostgreSQL on SMP Architectures |
| Previous Message | Reydan Cankur | 2010-02-14 16:36:24 | PostgreSQL on SMP Architectures |