Re: RFC: Making TRUNCATE more "MVCC-safe"

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Making TRUNCATE more "MVCC-safe"
Date: 2012-03-07 15:26:43
Message-ID: CA+U5nMLENSfpf1MOnww9ExKCt84=3=b2WicpMz+bjq5TkNbS6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 7, 2012 at 2:59 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> All true.

So gentlemen, do we think this is worth pursuing further for this release?

I'm sure usual arguments apply all round, so I'll skip that part.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-03-07 15:28:38 Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
Previous Message Simon Riggs 2012-03-07 15:17:10 Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)