| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | 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 |
| Date: | 2018-11-15 10:11:03 |
| Message-ID: | CAA4eK1+xTGad5fy2_9i0Ad-PR0DEvtW0PD-m4dHNiAX7OgqVVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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/c9374921e50a5e8fb1ecf04eb8c6ebc3%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.
>
+1.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ronan Dunklau | 2018-11-15 10:23:24 | ALTER INDEX ... ALTER COLUMN not present in dump |
| Previous Message | Kyotaro HORIGUCHI | 2018-11-15 09:14:50 | Re: [HACKERS] PATCH: Keep one postmaster monitoring pipe per process |