On 11/4/21, 3:24 AM, "Daniel Gustafsson" wrote:
> As no update has been posted, the patch still doesn't apply. I'm marking this
> patch Returned with Feedback, feel free to open a new entry for an updated
> patch.
Thanks. I have been working on this intermittently, and I hope to
post a more com
> On 14 Jul 2021, at 13:34, vignesh C wrote:
> The patch does not apply on Head anymore, could you rebase and post a
> patch. I'm changing the status to "Waiting for Author".
As no update has been posted, the patch still doesn't apply. I'm marking this
patch Returned with Feedback, feel free to
On Tue, Mar 9, 2021 at 12:09 AM Bossart, Nathan wrote:
>
> On 3/8/21, 10:16 AM, "Ibrar Ahmed" wrote:
> > On Wed, Feb 24, 2021 at 3:22 AM Bossart, Nathan wrote:
> >> On 2/10/21, 2:43 PM, "Bruce Momjian" wrote:
> >>> I wonder if you should create a Postgres wiki page to document all of
> >>> this
On Mon, Apr 19, 2021 at 5:09 PM Bruce Momjian wrote:
> > A diversity of strategies with fallback behavior is sometimes the best
> > strategy. Don't underestimate the contribution of rare and seemingly
> > insignificant adverse events. Consider the lifecycle of the data over
>
> That is an intersti
On Sun, Apr 18, 2021 at 04:27:15PM -0700, Peter Geoghegan wrote:
> Everybody tends to talk about HOT as if it works perfectly once you
> make some modest assumptions, such as "there are no long-running
> transactions", and "no UPDATEs will logically modify indexed columns".
> But I tend to doubt th
On Tue, Feb 9, 2021 at 10:48 AM Bossart, Nathan wrote:
> I'm hoping to gather some early feedback on a heap optimization I've
> been working on. In short, I'm hoping to add "partial heap only
> tuple" (PHOT) support, which would allow you to skip updating indexes
> for unchanged columns even when
On Tue, Mar 9, 2021 at 09:33:31PM +, Bossart, Nathan wrote:
> I'm cautiously optimistic that index creation and deletion will not
> require too much extra work. For example, if a new index needs to
> point to a partial heap only tuple, it can do so (unlike HOT, which
> would require that the
On 3/9/21, 8:24 AM, "Bruce Momjian" wrote:
> On Mon, Feb 15, 2021 at 08:19:40PM +, Bossart, Nathan wrote:
>> Yeah, this is something I'm concerned about. I think adding a bitmap
>> of modified columns to the header of PHOT-updated tuples improves
>> matters quite a bit, even for single-page v
On Mon, Feb 15, 2021 at 08:19:40PM +, Bossart, Nathan wrote:
> Yeah, this is something I'm concerned about. I think adding a bitmap
> of modified columns to the header of PHOT-updated tuples improves
> matters quite a bit, even for single-page vacuuming. Following is a
> strategy I've been de
On 3/8/21, 10:16 AM, "Ibrar Ahmed" wrote:
> On Wed, Feb 24, 2021 at 3:22 AM Bossart, Nathan wrote:
>> On 2/10/21, 2:43 PM, "Bruce Momjian" wrote:
>>> I wonder if you should create a Postgres wiki page to document all of
>>> this. I agree PG 15 makes sense. I would like to help with this if I
>
On Wed, Feb 24, 2021 at 3:22 AM Bossart, Nathan wrote:
> On 2/10/21, 2:43 PM, "Bruce Momjian" wrote:
> > I wonder if you should create a Postgres wiki page to document all of
> > this. I agree PG 15 makes sense. I would like to help with this if I
> > can. I will need to study this email more
On 2/10/21, 2:43 PM, "Bruce Momjian" wrote:
> I wonder if you should create a Postgres wiki page to document all of
> this. I agree PG 15 makes sense. I would like to help with this if I
> can. I will need to study this email more later.
I've started the wiki page for this:
https://wiki.p
On 2/13/21, 8:26 AM, "Andres Freund" wrote:
> On 2021-02-09 18:48:21 +, Bossart, Nathan wrote:
>> In order to be eligible for cleanup, the final tuple in the
>> corresponding PHOT/HOT chain must also be eligible for cleanup, or all
>> indexes must have been updated later in the chain before an
Hi,
On 2021-02-09 18:48:21 +, Bossart, Nathan wrote:
> In order to be eligible for cleanup, the final tuple in the
> corresponding PHOT/HOT chain must also be eligible for cleanup, or all
> indexes must have been updated later in the chain before any visible
> tuples.
This sounds like it migh
On 2/10/21, 2:43 PM, "Bruce Momjian" wrote:
> On Tue, Feb 9, 2021 at 06:48:21PM +, Bossart, Nathan wrote:
>> HOT works wonders when no indexed columns are updated. However, as
>> soon as you touch one indexed column, you lose that optimization
>> entirely, as you must update every index on t
On Tue, Feb 9, 2021 at 06:48:21PM +, Bossart, Nathan wrote:
> Hello,
>
> I'm hoping to gather some early feedback on a heap optimization I've
> been working on. In short, I'm hoping to add "partial heap only
> tuple" (PHOT) support, which would allow you to skip updating indexes
> for unchan
16 matches
Mail list logo
