From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [RFC] Minmax indexes |
Date: | 2013-06-15 15:39:23 |
Message-ID: | 7593.1371310763@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 15 June 2013 00:01, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> If we're going to start adding reloptions for specific table behavior,
>> I'd rather think of all of the optimizations we might have for a
>> prospective "append-only table" and bundle those, rather than tying it
>> to whether a certain index exists or not.
> I agree that the FSM behaviour shouldn't be linked to index existence.
> IMHO that should be a separate table parameter, WITH (fsm_mode = append)
> Index only scans would also benefit from that.
-1 ... I cannot believe that such a parameter would ever get turned on
in production by anyone. If your table has a significant update rate,
the resulting table bloat would make such behavior completely
infeasible. If you have few enough updates to make such a behavior
practical, then you can live with the expensive index updates instead.
I also find the analogy to index-only scans to be bogus, because those
didn't require any user tuning.
There's a nearby thread complaining bitterly about our willingness to
create hard-to-use, hard-to-tune "features". In its current form,
this will be another one of those.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-06-15 15:44:39 | Re: stray SIGALRM |
Previous Message | Simon Riggs | 2013-06-15 15:33:02 | Re: [RFC] Minmax indexes |