| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
| Cc: | Christopher Browne <cbbrowne(at)gmail(dot)com>, Israel Brewster <israel(at)brewstersoft(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PostgreSQL Mailing Lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Table partitioning for cloud service? |
| Date: | 2020-05-21 19:13:31 |
| Message-ID: | CAHOFxGrW2kqofDQcNuY-5gBGe2nNqm-uF-iHJcQ91sg9j+XXuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 21, 2020 at 11:41 AM Adam Brusselback <adambrusselback(at)gmail(dot)com>
wrote:
> As an optimization I just worked on for my database earlier this week, I
> decided to logically replicate that table from my main authentication
> database into a each cluster, and I replaced all references to the FDW for
> read-only queries to use the logically replicated table. All write queries
> still hit the FDW as before.
>
Perhaps you considered this, but if you had not wanted to deal with the
administration side with replication, and the centralized data is changed
infrequently from only one application/source perhaps, then updating the
source and then refreshing a materialized view on each local db that pulls
in the foreign data could be a good option. Some chance of stale data since
the refresh must be triggered, but for some use cases it may be the
simplest setup.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pabloa98 | 2020-05-21 19:28:26 | Re: Should I use JSON? |
| Previous Message | Adam Brusselback | 2020-05-21 17:41:10 | Re: Table partitioning for cloud service? |