| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)krosing(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MERGE Specification |
| Date: | 2008-04-25 12:54:34 |
| Message-ID: | 1209128074.4238.14.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2008-04-25 at 10:03 +0300, Hannu Krosing wrote:
> On Tue, 2008-04-22 at 00:24 +0100, Simon Riggs wrote:
> > On Mon, 2008-04-21 at 16:38 -0400, A.M. wrote:
> >
> > > "MERGE will not invoke Rules." Does this imply that MERGE cannot be
> > > used on views or that the resulting INSERTs or UPDATEs do not work on
> > > views?
> >
> > Yes, that's right. Just like COPY. That seems fine to me because you're
> > likely to be doing a MERGE immediately after a COPY anyway, so the
> > restriction just continues.
>
> May be the bulk data merging variant of MERGE to be used after initial
> COPY should be a variant of COPY with special keyword(s) instead of
> MERGE ?
That does sound like a good way of differentiating between the OLTP and
bulk loading cases.
I'll bear that in mind as we develop.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2008-04-25 13:04:50 | Re: Proposed patch - psql wraps at window width |
| Previous Message | Decibel! | 2008-04-25 12:45:15 | Re: MERGE Specification |