| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Avi Weinberg <AviW(at)gilat(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Subscriber to Get Only Some of The Tables From Publisher |
| Date: | 2021-09-09 09:16:37 |
| Message-ID: | CANbhV-Et0z=o_0NXcJVLmH9gUzJrvW5_yj9Z-MpxiD=+-Wh+cQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 9 Sept 2021 at 06:54, Avi Weinberg <AviW(at)gilat(dot)com> wrote:
> I have a publisher with around 30 tables. I have two types of subscribers. Both types needs 25 "common" tables from the publisher plus 2-3 specific tables for each type of subscriber.
>
> For maintenance and monitoring reasons it is better for me to have both subscribers point to the same publisher but "skip/ignore" 2-3 tables that are not needed for them. If this is not possible, I will be forced to create 2 publishers.
>
> Any idea hot to ignore tables from publisher?
That's not the way the APIs are defined.
Creating 2 publications should not be a problem.
Specifying the metadata for your situation would be about the same
complexity in all cases.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2021-09-09 09:58:23 | Re: ALTER DATABASE SET not working as expected? |
| Previous Message | Ian Lawrence Barwick | 2021-09-09 09:06:08 | Re: ALTER DATABASE SET not working as expected? |