--On 13. Juni 2014 13:46:38 -0400 Tom Lane wrote:
Imagine if `BeginForeignScan` set up a remote cursor and
`IterateForeignScan` just fetched _one tuple at a time_ (unlike the
current behavior where they are fetched in batches). The tuple would be
passed to `ExecForeignDelete` (as is required)
(2014/06/14 2:46), Tom Lane wrote:
> Jason Petersen writes:
>> Even if there is no guarantee that `IterateForeignScan` is called exactly
>> once
>> before each `ExecForeignDelete` call (which would remove the ability to have
>> them cooperate using this single cursor), one could easily devise ot
Jason Petersen writes:
> Imagine if `BeginForeignScan` set up a remote cursor and `IterateForeignScan`
> just fetched _one tuple at a time_ (unlike the current behavior where they are
> fetched in batches). The tuple would be passed to `ExecForeignDelete` (as is
> required), but the remote cursor
I've been deep in the FDW APIs lately and have come up with a couple of
questions about the [user-facing documentation][1].
# Requirement that DELETE use junk columns
The bit I'm confused by is the parenthetical in this bit at the end of the
section on `AddForeignUpdateTargets`:
> If the AddFore
