| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Write Ahead Logging for Hash Indexes |
| Date: | 2017-03-15 15:02:52 |
| Message-ID: | 3178.1489590172@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:
> That theory seems inconsistent with how mdextend() works. My
> understanding is that we zero-fill the new blocks before populating
> them with actual data precisely to avoid running out of disk space due
> to deferred allocation at the OS level. If we don't care about
> failures due to deferred allocation at the OS level, we can rip that
> logic out and improve the performance of relation extension
> considerably.
See my reply to Stephen. The fact that this fails to guarantee no
ENOSPC on COW filesystems doesn't mean that it's not worth doing on
other filesystems. We're reducing the risk, not eliminating it,
but reducing risk is still a worthwhile activity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafia Sabih | 2017-03-15 15:05:30 | Re: Enabling parallelism for queries coming from SQL or other PL functions |
| Previous Message | Tom Lane | 2017-03-15 14:57:15 | Re: [PATCH] Suppress Clang 3.9 warnings |