Re: tableam vs. TOAST - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: tableam vs. TOAST
Date
Msg-id 20190905145225.GA26835@alvherre.pgsql
Whole thread Raw
In response to Re: tableam vs. TOAST  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: tableam vs. TOAST
List pgsql-hackers
On 2019-Aug-05, Robert Haas wrote:

> > Shouldn't this condition be the other way round?
> 
> I had to fight pretty hard to stop myself from tinkering with the
> algorithm -- this can clearly be done better, but I wanted to make it
> match the existing structure as far as possible. It also only needs to
> be tested once, not on every loop iteration, so if we're going to
> start changing things, we should go further than just swapping the
> order of the tests.  For now I prefer to draw a line in the sand and
> change nothing.

I agree, and can we move forward with this 0001?  The idea here is to
change no code (as also suggested by Tom elsewhere), and it's the
largest patch in this series by a mile.  I checked --color-moved=zebra
and I think the patch looks fine, and also it compiles fine.  I ran
src/tools/pginclude/headerscheck on it and found no complaints.

So here's a rebased version, where the DETOAST_H whitespace has been
removed.  No other changes from your original.  Will you please push
soon?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: SegFault on 9.6.14
Next
From: Tom Lane
Date:
Subject: Re: Specifying attribute slot for storing/reading statistics