|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: reloption to prevent VACUUM from truncating empty pages at the end of relation|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2018-04-18 10:46:51 +0900, Michael Paquier wrote:
> On Tue, Apr 17, 2018 at 06:13:31PM -0700, Andres Freund wrote:
> > Not sure what you mean?
> Do you need help on it? I suggest that I could undertake the proposed
> patch and submit it earlier in the development cycle of v12.
I think it's at the very least two months of serious development work to
get it into a state ready for submission. And a good chunk of that not
even sketched out. Replacing the hashtable is the easy part, the memory
management (Complicated due to lock-freeness. I'm thinking of using a
variant of epoch based reclamation) isn't really there, the management
of shared "open relations" state are the hard parts...
So yes, I could use help on it, but it'll be a lot of actual design and
|Next Message||Amit Langote||2018-04-18 02:52:41||Re: pruning disabled for array, enum, record, range type partition keys|
|Previous Message||Wood, Dan||2018-04-18 02:07:17||VM map freeze corruption|