Re: documentation on HOT

2022-08-12 Thread Bruce Momjian
On Tue, Jul 26, 2022 at 07:29:10PM -0400, Bruce Momjian wrote: > > Summary paragraph: > > "can only happen if" => "can only be created if" > > Yes, good point. > > Updated patch attached. I applied this patch back to PG 11. (PG 10 had too many conflicts.) I also added a mention about how

Re: documentation on HOT

2022-07-26 Thread Bruce Momjian
On Sat, Jul 23, 2022 at 12:12:38PM -0700, David G. Johnston wrote: > I concur, suggesting the following: > > "Specifically, updates result in multiple rows versions (tuples) existing on > the table." See my reply to Peter G. about tuples. > "There is sufficient free space on the page containing

Re: documentation on HOT

2022-07-26 Thread Bruce Momjian
On Sat, Jul 23, 2022 at 11:33:40AM -0700, Peter Geoghegan wrote: > On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote: > > Good points. I have updated the attached patch and URL to mention that > > HOT rows are _completely_ removed, and why that is possible, and I > > clarified the page item

Re: documentation on HOT

2022-07-23 Thread David G. Johnston
On Sat, Jul 23, 2022 at 11:34 AM Peter Geoghegan wrote: > On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote: > > Good points. I have updated the attached patch and URL to mention that > > HOT rows are _completely_ removed, and why that is possible, and I > > clarified the page item

Re: documentation on HOT

2022-07-23 Thread Peter Geoghegan
On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote: > Good points. I have updated the attached patch and URL to mention that > HOT rows are _completely_ removed, and why that is possible, and I > clarified the page item identifier mention. I think that this version looks very good, but I do

Re: documentation on HOT

2022-07-23 Thread Bruce Momjian
On Fri, Jul 22, 2022 at 03:33:20PM -0700, Peter Geoghegan wrote: > On Fri, Jul 22, 2022 at 2:11 PM Bruce Momjian wrote: > > I have improved the wording of the last paragraph in this patch. > > I think that it would be worth prominently explaining where heap-only > tuples get their name from: it

Re: documentation on HOT

2022-07-22 Thread Peter Geoghegan
On Fri, Jul 22, 2022 at 2:11 PM Bruce Momjian wrote: > I have improved the wording of the last paragraph in this patch. I think that it would be worth prominently explaining where heap-only tuples get their name from: it comes from the fact there are (by definition) no entries for a heap-only

Re: documentation on HOT

2022-07-22 Thread Bruce Momjian
On Fri, Jul 22, 2022 at 01:07:41PM -0400, Bruce Momjian wrote: > > > You can increase the change of HOT updates by using non-default table > > fillfactor settings. > > > > I think we should expand on this and explain how adjusting "fillfactor" will > > affect this. I think that may change the

Re: documentation on HOT

2022-07-22 Thread Bruce Momjian
On Fri, Jul 22, 2022 at 10:05:04AM -0700, Peter Geoghegan wrote: > On Fri, Jul 22, 2022 at 8:09 AM Jonathan S. Katz wrote: > > Thanks! This is great. Probably the most concise and clear explanation I > > have seen for HOT, which is exactly what we need for the docs :) > > I'm delighted that this

Re: documentation on HOT

2022-07-22 Thread Bruce Momjian
On Fri, Jul 22, 2022 at 09:25:43AM -0700, David G. Johnston wrote: > On Fri, Jul 22, 2022 at 8:09 AM Jonathan S. Katz wrote: > I think we need to expose the information regarding columns used in predicates > here. > > "(Here, "indexed column" means any column referenced > at all in an index

Re: documentation on HOT

2022-07-22 Thread Bruce Momjian
On Fri, Jul 22, 2022 at 11:09:49AM -0400, Jonathan Katz wrote: > On 7/22/22 8:51 AM, Bruce Momjian wrote: > > URL contents updated too: > > > > https://momjian.us/tmp/pgsql/storage-hot.html > > Thanks! This is great. Probably the most concise and clear explanation I > have seen for HOT,

Re: documentation on HOT

2022-07-22 Thread Peter Geoghegan
On Fri, Jul 22, 2022 at 8:09 AM Jonathan S. Katz wrote: > Thanks! This is great. Probably the most concise and clear explanation I > have seen for HOT, which is exactly what we need for the docs :) I'm delighted that this is finally happening! > I think we should expand on this and explain how

Re: documentation on HOT

2022-07-22 Thread David G. Johnston
On Fri, Jul 22, 2022 at 8:09 AM Jonathan S. Katz wrote: > On 7/22/22 8:51 AM, Bruce Momjian wrote: > > On Thu, Jul 21, 2022 at 10:02:18PM -0400, Bruce Momjian wrote: > >> On Sun, Feb 6, 2022 at 09:29:56PM -0500, Jonathan Katz wrote: > >>> I agree with Bruce's point that we should have a new

Re: documentation on HOT

2022-07-22 Thread Jonathan S. Katz
On 7/22/22 8:51 AM, Bruce Momjian wrote: On Thu, Jul 21, 2022 at 10:02:18PM -0400, Bruce Momjian wrote: On Sun, Feb 6, 2022 at 09:29:56PM -0500, Jonathan Katz wrote: I agree with Bruce's point that we should have a new section (or subsection). As I mentioned in my previous post, given HOT

Re: documentation on HOT

2022-07-22 Thread Bruce Momjian
On Thu, Jul 21, 2022 at 10:02:18PM -0400, Bruce Momjian wrote: > On Sun, Feb 6, 2022 at 09:29:56PM -0500, Jonathan Katz wrote: > > I agree with Bruce's point that we should have a new section (or > > subsection). As I mentioned in my previous post, given HOT involves > > indexing, I would suggest

Re: documentation on HOT

2022-07-21 Thread Bruce Momjian
On Sun, Feb 6, 2022 at 09:29:56PM -0500, Jonathan Katz wrote: > I agree with Bruce's point that we should have a new section (or > subsection). As I mentioned in my previous post, given HOT involves > indexing, I would suggest putting it there. > > I think that something that follows the general

Re: documentation on HOT

2022-02-06 Thread Jonathan S. Katz
On 2/6/22 8:56 PM, David G. Johnston wrote: On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz > wrote: Given the importance of HOT, it seems like this would be a good topic to document. I would suggest something higher-level for general users in the

Re: documentation on HOT

2022-02-06 Thread David G. Johnston
On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz wrote: > > Given the importance of HOT, it seems like this would be a good topic to > document. I would suggest something higher-level for general users in > the "Indexes"[4] section, and something lower-level in internals[5] > (which could perhaps