|From:||"Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>|
|To:||'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <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 Thu, Nov 15, 2018 at 2:30 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> On 2018-Nov-15, Laurenz Albe wrote:
> > > This new option would not only mitigate the long shared_buffers
> > > scan, it would also get rid of the replication conflict caused by
> > > the AccessExclusiveLock taken during truncation, which is discussed
> > > in
> > > https://www.postgresql.org/message-id/c9374921e50a5e8fb1ecf04eb8c6eb
> > > c3%40postgrespro.ru and seems to be a more difficult problem than
> > > anticipated.
> > FWIW I was just reminded yesterday that the AEL-for-truncation has
> > been diagnosed to be a severe problem in production, and with no other
> > solution in sight, I propose to move forward with the stop-gap.
I just want to ask whether or not we could proceed with this approach for now and
if it is possible that we could have this solution integrated before PG12 development ends?
|Next Message||Michael Paquier||2019-01-17 00:54:16||Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name|
|Previous Message||Erik Rijkers||2019-01-16 21:40:59||Re: [HACKERS] generated columns|