| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pabloa98 <pabloa98(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: is it possible to create partitioned tables using tables from different schemas |
| Date: | 2019-04-18 00:17:46 |
| Message-ID: | fa8e7504-c59f-6908-1fe9-4eec4dea7c56@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/17/19 3:56 PM, Alvaro Herrera wrote:
> Note that unless you regularly query for only-manually-inserted or
> only-automatically-inserted data, this will be useless and will make
> queries more expensive, with no upside.
Well the OP's use case is:
"I would like to store in that table manually generated information.
Since those rows are inserted by hand, they will be lost when the table
will be reimported."
This got me to thinking an INSERT trigger would work also.
>
> Generally speaking, it's not a problem to put partitions in different
> schemas.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julie Nishimura | 2019-04-18 00:18:40 | ERROR: operator class "gin__int_ops" does not exist for access method "gin" |
| Previous Message | Alvaro Herrera | 2019-04-17 22:56:48 | Re: is it possible to create partitioned tables using tables from different schemas |