public inbox for [email protected]
help / color / mirror / Atom feedFrom: Amit Langote <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: David Rowley <[email protected]>
Cc: Justin Clift <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: [email protected]
Subject: Re: PostgreSQL 12: Feature Highlights
Date: Wed, 15 May 2019 09:34:10 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAKJS1f-1=BoVkJaTnfb87nrVUFLprdc7smsBsF5MGyCXnNivzw@mail.gmail.com>
<[email protected]>
<CAKJS1f9=xUz5y=VDy6hYMVpSoej9+D2BminegmfqHwdWQfpQ9w@mail.gmail.com>
<[email protected]>
<CAKJS1f84HJj3qiDzpX9-iz_6AAdiX7khtgUf0UPVEmEd3YZ4hQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
On 2019/05/14 22:19, Bruce Momjian wrote:
> On Tue, May 14, 2019 at 06:25:43PM +0900, Amit Langote wrote:
>> Considering the quoted discussion here, maybe it's a good idea to note
>> that only the operations that need to touch a small number of partitions
>> are now processed efficiently, which covers both SELECT/UPDATE/DELETE that
>> benefit from improved pruning efficiency and INSERT that benefit from
>> improved tuple routing efficiency. So, maybe:
>>
>> Tables with thousands of child partitions can now be processed
>> efficiently by operations that only need to touch a small number
>> of partitions.
>>
>> That is, as I mentioned above, as opposed to queries that need to process
>> all partitions (such as, select count(*) from partitioned_table), which
>> don't perform any faster in v12 than in v11. The percentage of users who
>> run such workloads on PostgreSQL may be much smaller today, but perhaps
>> it's not a good idea to mislead them into thinking that *everything* with
>> partitioned tables is now faster even with thousands of partitions.
>
> Agreed, I changed it to your wording.
Thank you.
Regards,
Amit
view thread (63+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: PostgreSQL 12: Feature Highlights
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox