Re: Design for In-Core Logical Replication - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Design for In-Core Logical Replication
Date
Msg-id dfc7a1b1-c712-24ef-d671-712407cc0f46@BlueTreble.com
Whole thread Raw
In response to Design for In-Core Logical Replication  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
ISTM pg_dump should alter publication/subscription when doing partial 
dumps, similar to how it handles foreign keys.

Subscribed tables should be read-only by default. If you need something 
more advanced than that adding an extra option to the subscription (or 
wherever else) is going to be the least of your worries. If we don't 
want to get too wrapped up in config/syntax I think there should at 
least be a read-only statement level trigger installed by default that 
users can then drop or disable if desired.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Re: Unexpected memory usage for repeated inserts within plpgsql function
Next
From: Jim Nasby
Date:
Subject: Re: Design for In-Core Logical Replication