Re: [PATCHES] [Fwd: Index Advisor] - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: [PATCHES] [Fwd: Index Advisor]
Date
Msg-id 65937bea0704120555x7e41ff54l372b7e80445d0e1@mail.gmail.com
Whole thread Raw
In response to Re: [PATCHES] [Fwd: Index Advisor]  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers

On 4/12/07, Bruce Momjian <bruce@momjian.us> wrote:
Gurjeet Singh wrote:
>     The interface etc. may not be beautiful, but it isn't ugly either! It is
> a lot better than manually creating pg_index records and inserting them into
> cache; we use index_create() API to create the index (build is deferred),
> and then 'rollback to savepoint' to undo those changes when the advisor is
> done. index_create() causes pg_depends entries too, so a 'RB to SP' is far
> much safer than going and deleting cache records manually.

My complaint was not that the API used in the code was non-optimal(which
I think was Tom's issue), but that the _user_ API was not very clean.
Not sure what to recommend, but I will think about it later.


That can be fixed/improved with minimal efforts, but if it is the internal API usage, or the architecture we're bothered about, then IMO just an overhaul of the code will not be sufficient, rather, it will require rework from scratch.

Best regards,
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com

17°29'34.37"N  78°30'59.76"E - Hyderabad
18°32'57.25"N  73°56'25.42 "E - Pune *

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: elog(FATAL) vs shared memory
Next
From: NikhilS
Date:
Subject: Re: Bug about column references within subqueries used in selects