Michael Renner <michael.ren...@amd.co.at> writes: > I've written a simple tool to generate traffic on a database , which > did about 30 TX/inserts per second to a table. Upon inspecting the data > in the table, I noticed the expected grouping of tuples which came from > a single backend to matching pages . The strange part was that the > pages weren't completely filled but the backends seemed to jump > arbitrarily from one page to the next . For the table in question > this resulted in about 10% wasted space.
Which table would that be? The trigger-driven updates to "auction", in particular, would certainly guarantee some amount of "wasted" space. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers