| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Design for In-Core Logical Replication |
| Date: | 2016-07-23 01:31:04 |
| Message-ID: | dfc7a1b1-c712-24ef-d671-712407cc0f46@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-07-23 01:31:07 | Re: Design for In-Core Logical Replication |
| Previous Message | Dilip Kumar | 2016-07-23 01:14:25 | Re: Re: Unexpected memory usage for repeated inserts within plpgsql function |