Hi Jeff,
The Pg error is presumably correct; is it possible there are multiple tables
named such (different search_path, say)? I’d expect that if so it’s just
trying to copy rows which have already been populated (via onetimecopy or
similar, though it looks like that’s not set, per the sync st
Hi, David, thanks for the reply. We were able to resolve this. Turns out
the error I posted was a red herring, and had no relevance. Which leads me
to a separate question, but I'll describe our resolution, first. I'll post
the details for closure's sake.
So, the problem turned out to be that there
> On Feb 8, 2018, at 9:35 AM, Jeff Silverman wrote:
>
> Hi, David, thanks for the reply. We were able to resolve this. Turns out the
> error I posted was a red herring, and had no relevance. Which leads me to a
> separate question, but I'll describe our resolution, first. I'll post the
> detai
