Re: Different table schema in logical replication crashes

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Different table schema in logical replication crashes
Date: 2017-04-17 12:47:26
Message-ID: CAHE3wgh9qLmjoOC4S5YO=FHq4C664Ny+n0qZbBpkJybdb7zeZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-04-14 22:36 GMT-03:00 Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>:

> I tried something bit different which seems cleaner to me - use the
> pstate->r_table instead of ad-hock locally made up range table and fill
> that using standard addRangeTableEntryForRelation. Both in tablesync and
> in DoCopy instead of the old coding.
>

Patch works fine. However, I don't see any documentation about supporting
different schemas for logical replication. Is it an oversight?

--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stas Kelvich 2017-04-17 13:59:35 Re: Logical replication - TRAP: FailedAssertion in pgstat.c
Previous Message Petr Jelinek 2017-04-17 12:46:42 Re: Re: logical replication and PANIC during shutdown checkpoint in publisher