Comments on: PostgreSQL: The Awesome Table Fillfactor to speedup UPDATE and SELECT statement https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/ BIGData | NoSQL | MSSQL | MySQL | PostgreSQL Wed, 11 Oct 2017 11:06:38 +0000 hourly 1 https://wordpress.org/?v=7.0.6 By: Dima https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/#comment-5742 Sun, 16 Jul 2017 13:52:19 +0000 https://www.dbrnd.com/?p=2188#comment-5742 In reply to Anvesh Patel.

It should be good to mention, that this only works when updates do not touch indexed columns.
When update touches indexed column(s), postgres should add new tuples to all table indexes to point to new version.

]]> By: Ayushi https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/#comment-5716 Tue, 04 Jul 2017 10:08:26 +0000 https://www.dbrnd.com/?p=2188#comment-5716 Simple and easily understandable terms and language
Thanks 🙂

]]> By: Anvesh Patel https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/#comment-5359 Wed, 12 Oct 2016 18:03:12 +0000 https://www.dbrnd.com/?p=2188#comment-5359 In reply to Venkatesh Naicker.

Hello Venkatesh,
Thanks for you appreciation !
When we are talking about same page operation, index pointer does not require to move from one page to another. Yes, It reduces most of I/O cost. Its also reduces the internal fragmentation.

]]> By: Venkatesh Naicker https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/#comment-5358 Wed, 12 Oct 2016 18:02:26 +0000 https://www.dbrnd.com/?p=2188#comment-5358 Hi Anvesh. Your post on the fill factor is interesting. You mentioned three i/o for an update with fill factor of 100 (1. delete original tuple, 2. insert new tuple on the new page, 3. update index). Now when there is fill factor of 70, doesn’t it still need to delete original tuple and insert the new tuple (though on the same page)? Is it saving on index update because on the same page? I am a bit lost? Thanks!

]]> By: bon https://www.dbrnd.com/2016/03/postgresql-the-awesome-table-fillfactor-to-speedup-update-and-select-statement/#comment-4177 Wed, 30 Mar 2016 05:33:45 +0000 https://www.dbrnd.com/?p=2188#comment-4177 Good way of describing, and fastidious piece of writing to get data
regarding my presentation subject matter, which i am going
to deliver in college.

]]>