Re: Dynamic creation of list partitions in highly concurrent write environment

From: Jim Vanns <jvanns(at)ilm(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Dynamic creation of list partitions in highly concurrent write environment
Date: 2023-06-01 13:45:05
Message-ID: CAH7vdhMjZbScgiUNLgsO7Zc_MVoexoaBx8tC41nKZVpKk5aX=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yeah, that's a known concern - hence the evaluation as part of the list
vs. hash comparison ;)

Jim

On Thu, 1 Jun 2023 at 14:32, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Jim Vanns <jvanns(at)ilm(dot)com> writes:
> > Here's the general approach we have, without code and with hypothetical
> > model, since I'm writing this hastily;
>
> > table devices; <-- After trigger on here
> > table routes; <-- To create physical partition for this logical table
> > table route_for_device_N; <-- The dynamically created partition
>
> > We don't know the device names and thus partitions up front, hence the
> need
> > for dynamic creation. How do you go about doing this or is it folly!?
>
> Sounds like folly, TBH. You're going to end with a ridiculous number
> of partitions of the routes table, which will not be good for performance.
>
> regards, tom lane
>

--
Jim Vanns
Principal Production Engineer
Industrial Light & Magic, London

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-06-01 15:03:53 Re: speed up full table scan using psql
Previous Message Tom Lane 2023-06-01 13:32:17 Re: Dynamic creation of list partitions in highly concurrent write environment