pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Noah Misch <noah@leadboat.com>
Subject: Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
Date: Mon, 22 Jul 2024 11:49:53 -0400
Message-ID: <890165.1721663393@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-Wzkrowjc2v-DML0zA2gHF=+KzFvodoyPKR-4hLND7XVZsQ@mail.gmail.com>
References: <CAAKRu_bDD7oq9ZwB2OJqub5BovMG6UjEYsoK2LVttadjEqyRGg@mail.gmail.com>
	<CAH2-WzkZUDr8TQDPuax1SmJg9B5yz-Qhr7NdoQJD5PpXLAUA7Q@mail.gmail.com>
	<acbce1b9-e88e-4a33-9fa7-4728f67454f2@iki.fi>
	<CAAKRu_apNU2MPBK96V+bXjTq0RiZ-=A4ZTaysakpx9jxbq1dbQ@mail.gmail.com>
	<CAAKRu_Z4PybtZ0i_NKOr-vbrFW5p1ZdfEfUqaeU8fLPhszpP_g@mail.gmail.com>
	<CAH2-WzmXqaX37VCVjTDBF5cauzUgXOkuXsSTLOq56EAB1vzkeQ@mail.gmail.com>
	<CAAKRu_b49z=TSUZG+i0NCEPW409wqsb3Y4MCaMRBVC6ZWKBeVw@mail.gmail.com>
	<CAAKRu_bQFifK3U=VGKpR5MXLaCWHZ-jf0N6xJvMnf_XYB2OR9A@mail.gmail.com>
	<CAH2-WznnDZgZAOUins9ye8_=Y=892N2mvjs9bUB8s37gXnOKQQ@mail.gmail.com>
	<CAAKRu_b+9i71Kk4MB3SxFMzox84En=v+X31sFvRzJ-ZsXVi0qw@mail.gmail.com>
	<614152.1721580711@sss.pgh.pa.us>
	<CAH2-Wz=3TJ86JF_Puv7zThOxZKAVyiNZED_4bxGEdRyftGY5Vg@mail.gmail.com>
	<CAAKRu_anqNS0R7z6M=swns0EV+RKHcbM_ELOJihNtnP3m8rwcw@mail.gmail.com>
	<CAH2-Wzkrowjc2v-DML0zA2gHF=+KzFvodoyPKR-4hLND7XVZsQ@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> On Mon, Jul 22, 2024 at 9:32 AM Melanie Plageman
> <melanieplageman@gmail.com> wrote:
>> Andres has suggested in the past that we allow maintenance_work_mem be
>> set to a lower value or introduce some kind of development GUC so that
>> we can more easily test multiple pass index vacuuming. Do you think
>> this would be worth it?

> No, I don't.

I don't see why that's not a good idea.

			regards, tom lane





view thread (92+ messages)  latest in thread

Message-ID: <890165.1721663393@sss.pgh.pa.us>
Permalink:  ../890165.1721663393@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/890165.1721663393@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, melanieplageman@gmail.com, hlinnaka@iki.fi, andres@anarazel.de, noah@leadboat.com
  Subject: Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
  In-Reply-To: <890165.1721663393@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox