From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Physical append-only tables |
Date: | 2016-11-14 14:41:38 |
Message-ID: | CABUevEx0JcJxjfmmPy=q3F7f2QLg234=U1KXkyRBrup5tt9z2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 14, 2016 at 3:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > What I'm talking about is something that would be a lot simpler than
> > auto-clustering. I'm not even talking about trying to detect if the row
> was
> > about to go into the right place -- this might be expensive and certainly
> > more complicated. I'm only talking about a simple case where we *never*
> put
> > anything anywhere other than at the end of the table, period. That should
> > make the check both cheap and simple.
>
> It also makes it so much of a corner case that even a cheap check could be
> a net performance degradation, especially for people whose usage pattern
> doesn't match this.
>
>
I agree that it definitely solves just one problem. But it seems to be a
fairly common problem, particularly for users of BRIN users.
Full auto-clustering would cover many more usecases, but would also be a
lot more expensive to maintain.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-14 14:45:29 | Re: Partition-wise join for join between (declaratively) partitioned tables |
Previous Message | Tom Lane | 2016-11-14 14:39:35 | Re: Physical append-only tables |