From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: do only critical work during single-user vacuum? |
Date: | 2022-02-04 22:56:45 |
Message-ID: | CAFBsxsFfPgH9Mwjk2cSj2Uaxwss0P3cBg_UdmyNonWx3trFi-w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 3, 2022 at 7:30 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> That error comes from GetNewTransactionId(), so that function must
> either try to execute DML or do something else which causes an XID to
> be assigned. I think a plain SELECT should work just fine.
It was indeed doing writes, so that much is not a surprise anymore.
On Thu, Feb 3, 2022 at 9:08 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Feb 3, 2022 at 8:35 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Yea, I'd have no problem leaving the "hard" limit somewhere closer to 1
> > million (although 100k should be just as well), but introduce a softer "only
> > vacuum/drop/truncate" limit a good bit before that.
>
> +1.
Since there seems to be agreement on this, I can attempt a stab at it,
but it'll be another week before I can do so.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Mlodgenski | 2022-02-04 23:25:31 | Re: support for CREATE MODULE |
Previous Message | Nathan Bossart | 2022-02-04 22:50:57 | Re: pg_walfile_name uses XLByteToPrevSeg |