From: | pabloa98 <pabloa98(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <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 02:07:30 |
Message-ID: | CAEjudX55OWvDJ=2GhUVbZwAZ4ZwjDmQvYK5nmEne_S31MgZ_Qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
you are right. What it happens is that the batch importing process drops
the schema and recreates it. I would like some solution that is compatible
with that.
I am sure partitioned tables will have an impact but on the other hand, it
will solve the problem I have now without touching the legacy code.
On Wed, Apr 17, 2019 at 6:41 PM David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:
> On Thu, 18 Apr 2019 at 10:56, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> 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.
>
> Going by "Since those rows are inserted by hand, they will be lost
> when the table will be reimported.", I just imagined there must be
> some sort of TRUNCATE + INSERT/COPY operation going on, in which case
> there would be a good upside of not having to perform a DELETE of all
> automatic records instead of the TRUNCATE.
>
> I could be wrong to assume that though.
>
> --
> David Rowley http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | pabloa98 | 2019-04-18 02:07:57 | Re: is it possible to create partitioned tables using tables from different schemas |
Previous Message | David Rowley | 2019-04-18 01:42:34 | Re: is it possible to create partitioned tables using tables from different schemas |