Re: Patch queue triage

Pavan Deolasee wrote:

>
> I suppose inserting HOT tuples without index maintenance is useful
> even if no
> changes to the space allocation is made is useful. It won't get the
> space
> usage but it would save on index thrashing. But that still implies
> all the
> code to handle scans, updates, index builds, etc. Those chunks could be
> separated out but you can't commit without them.
>
>
>
> There are few things that we can separate easily, like CREATE INDEX
> related changes, VACUUM and VACUUM FULL related changed, space
> reuse related changes etc. Let me give it a shot.

Did we ever get a broken up patch for this?

Joshua D. Drake

>
> Thanks,
> Pavan
>
>
> --
>
> EnterpriseDB http://www.enterprisedb.com

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/