| From: | Chris Morris <chris(at)mysteryscience(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG 12: Partitioning across a FDW? |
| Date: | 2020-03-25 17:38:29 |
| Message-ID: | CALrUc2XAmvYFjGf0nEC6EzzvbWhOSJ1ByT-BOyH1i9VBKNCUkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Right now my dbs are hosted by Heroku, so I doubt I have any control over
the dbs at that level.
Thanks for the idea though! :)
On Wed, Mar 25, 2020 at 12:04 PM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
> Chris,
> Does it actually need to be a different server and database, or would it
> be possible to have another storage device added to your existing database
> and make use of tablespaces to accomplish pseudo-archive of older
> partitions? Just a thought.
>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Magoffin | 2020-03-26 00:23:49 | Re: Duplicate key violation on upsert |
| Previous Message | Michael Lewis | 2020-03-25 17:03:54 | Re: PG 12: Partitioning across a FDW? |