Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I'm wondering if this problem could be solved with a sort of
> mark-and-sweep garbage collection:
> Then you can write something which goes through and sets all the rows
> to false and then visits every row of every table in the database and
> forces OID lookups on the security ID of each. When you get done, any
> rows that still say false are unreferenced and can be killed.
This sounds awfully similar to the bitmap index vacuum problem. I wonder if
security labels could be implemented as some kind of funky special index.
Just thinking out loud. I don't have a well-formed idea based on this.
Ask me about EnterpriseDB's 24x7 Postgres support!
In response to
pgsql-hackers by date
|Next:||From: Gregory Stark||Date: 2009-01-29 11:08:06|
|Subject: Re: Commitfest infrastructure|
|Previous:||From: Magnus Hagander||Date: 2009-01-29 10:30:02|
|Subject: Re: mingw check hung|