| From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com> |
| Cc: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>,"Robert Haas" <robertmhaas(at)gmail(dot)com>,"Marti Raudsepp" <marti(at)juffo(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TRUNCATE SERIALIZABLE and frozen COPY |
| Date: | 2012-11-09 16:03:05 |
| Message-ID: | 20121109160305.77850@gmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> My goal is to allow COPY to load frozen tuples without causing MVCC
> violations.
OK. That wasn't initially clear to me.
> Forcing a tightly scoped proposal into a much wider one will just
> kill this and leave it blocked.
The goal is important enough and narrow enough to merit the approach
you're talking about, IMV, at least. Sorry I initially misunderstood
what you were going for.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Reykja | 2012-11-09 16:09:51 | Re: DEALLOCATE IF EXISTS |
| Previous Message | Simon Riggs | 2012-11-09 16:00:34 | Re: TRUNCATE SERIALIZABLE and frozen COPY |