Re: [HACKERS] Different table schema in logical replication crashes - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Different table schema in logical replication crashes
Date
Msg-id b52f2775-3ab5-ca7c-ae34-924f78757195@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Different table schema in logical replication crashes  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] Different table schema in logical replication crashes
Re: [HACKERS] Different table schema in logical replication crashes
List pgsql-hackers
On 4/14/17 08:49, Petr Jelinek wrote:
>> Are we prepared to support different schemas in v10? Or should we
>> disallow it for v10 and add a TODO?
>>
> 
> Ah nuts, yes it's supposed to be supported, we seem to not initialize
> cstate->range_table in tablesync which causes this bug. The CopyState
> struct is private to copy.c so we can't easily set cstate->range_table
> externally. I wonder if tablesync should just construct CopyStmt instead
> of calling the lower level API.

Maybe pass the range_table to BeginCopyFrom so that it can write it into
cstate?

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] [pgsql-www] Small issue in online devel documentation build
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [pgsql-www] Small issue in online devel documentationbuild