Re: On disable_cost

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: On disable_cost
Date: 2024-10-07 15:57:36
Message-ID: 39961576967f3be077e66bfc9b9011c6dfadd5af.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2024-10-07 at 11:14 -0400, Robert Haas wrote:
> I accept that my commit created this problem and I'm
> certainly willing to be involved too if we need to sort out more
> things.

Thanks you. I think it is great that disabled nodes are now handled
better, so I appreciate the change as such. But I had to focus on
the one fly in the ointment; you know how it is...

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-10-07 15:58:54 Re: Should rolpassword be toastable?
Previous Message Robert Haas 2024-10-07 15:52:27 Re: Proposal to Enable/Disable Index using ALTER INDEX