| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 9.3: load path to mitigate load penalty for checksums |
| Date: | 2012-06-12 16:12:00 |
| Message-ID: | 18085.1339517520@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Tue, Jun 12, 2012 at 7:42 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Instead of trying to maintain MVCC semantics, maybe we should just
>> have something like COPY (FROZEN) that just writes frozen tuples into
>> the table and throws MVCC out the window. Seems like that would be a
>> lot easier to implement and satisfy basically the same use cases.
> -1: The situation with hint bit i/o patterns on many workloads is
> untenable but it's not safe to assume MVCC can be ditched in those
> workloads. Also, COPY does nothing about deletes. Neither does the
> proposal as stated but I think it's easier to generalize into 'I want
> to put hint bits in now so I don't have to deal with them later'.
Dunno, I think Robert's idea has a fair amount of merit: mainly because
it will probably satisfy 90% of use cases for 1% of the work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-12 16:27:57 | Re: xml_is_document and selective pg_re_throw |
| Previous Message | Merlin Moncure | 2012-06-12 15:55:56 | Re: 9.3: load path to mitigate load penalty for checksums |