On Thu, Jun 2, 2011 at 10:57 AM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Excerpts from Merlin Moncure's message of jue jun 02 11:33:28 -0400 2011: >> On Thu, Jun 2, 2011 at 10:02 AM, Alvaro Herrera >> <alvhe...@commandprompt.com> wrote: > >> > Seems pretty wasteful if you want to delete a single tuple from a large >> > result. I think if you desired to compact the result to free some >> > memory after deleting a large fraction of the tuples in the result it >> > could be useful to do that, otherwise just live with the unused holes in >> > the storage area as suggested by Pavel. >> >> That would work, but it would potentially invalidate external pointers >> to internal result data. If you wanted to do this, it might be better >> to expose a compaction feature which can be invoked directly. > > Wouldn't that also invalidate external pointers?
sure -- but at least they are being deliberately invalidated instead of automatically through some other function (i'm thinking about the stl vector pointer invalidation issues here). also since compaction could be fairly slow, it would be hard to exactly judge when it should be done. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
