Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0697F9FB51D for ; Tue, 23 Jan 2007 04:48:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 05296-10 for ; Tue, 23 Jan 2007 04:48:49 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svana.org (calyx.svana.org [125.62.87.134]) by postgresql.org (Postfix) with ESMTP id 18ED59FB26E for ; Tue, 23 Jan 2007 04:48:49 -0400 (AST) Received: from kleptog by svana.org with local (Exim 4.50) id 1H9HKh-0005ou-0J; Tue, 23 Jan 2007 19:48:47 +1100 Date: Tue, 23 Jan 2007 09:48:46 +0100 From: Martijn van Oosterhout To: Pavan Deolasee Cc: pgsql-hackers@postgresql.org Subject: Re: Free space management within heap page Message-ID: <20070123084846.GC19527@svana.org> Reply-To: Martijn van Oosterhout References: <2e78013d0701230018m7bebdd35t32bdc8ea786511e8@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE" Content-Disposition: inline In-Reply-To: <2e78013d0701230018m7bebdd35t32bdc8ea786511e8@mail.gmail.com> X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kleptog@svana.org X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/1035 X-Sequence-Number: 96936 --nmemrqcdn5VTmUEE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 23, 2007 at 01:48:08PM +0530, Pavan Deolasee wrote: > I am thinking that maintaining fragmented free space within a heap page > might be a good idea. It would help us to reuse the free space ASAP witho= ut > waiting for a vacuum run on the page. This in turn will lead to lesser he= ap > bloats and also increase the probability of placing updated tuple in the > same heap page as the original one. Nice idea but: > We might not be able to reuse the line pointers because indexes may have > references to it. All such line pointers will be freed when the page is > vacuumed during the regular vacuum. The overwhelming vast majoirty of tuples are going to be in one or more indexes. Which means nearly all tuples are going to fall into this category. So where's the benefit? Have a nice day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to l= itigate. --nmemrqcdn5VTmUEE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFtcvuIB7bNG8LQkwRAsDLAJ4sPvR9jbe02jlNNN2zqHbovZGnDgCeMYHU weocjbIYcVic+o3bx4TbJF8= =2uHt -----END PGP SIGNATURE----- --nmemrqcdn5VTmUEE--