Re: Logical Replication WIP - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Logical Replication WIP
Date
Msg-id 4f0bb8cb-7dd4-7242-f9ec-55ce421e1f09@2ndquadrant.com
Whole thread Raw
In response to Re: Logical Replication WIP  (Andres Freund <andres@anarazel.de>)
Responses Re: Logical Replication WIP  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 9/14/16 11:21 AM, Andres Freund wrote:
>> +    ExecInsert(NULL, /* mtstate is only used for onconflict handling which we don't support atm */
>> > +               remoteslot,
>> > +               remoteslot,
>> > +               NIL,
>> > +               ONCONFLICT_NONE,
>> > +               estate,
>> > +               false);
> I have *severe* doubts about just using the (newly) exposed functions
> 1:1 here.

It is a valid concern, but what is the alternative?  ExecInsert() and
the others appear to do exactly the right things that are required.

Are your concerns mainly philosophical about calling into internal
executor code, or do you have technical concerns that this will not do
the right thing in some cases?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Vacuum: allow usage of more than 1GB of work mem
Next
From: Kuntal Ghosh
Date:
Subject: Re: WAL consistency check facility