On Mon, 2011-10-24 at 13:15 +0300, Heikki Linnakangas wrote:
> Hmm, I don't think that's safe. After Oid wraparound, a range type oid
> might get reused for some other range type, and the cache would return
> stale values. Extremely unlikely to happen by accident, but could be
> exploited by an attacker.
Any ideas on how to remedy that? I don't have another plan for making it
perform well. Plugging it into the cache invalidation mechanism seems
like overkill, but I suppose that would solve the problem.
Aren't there a few other cases like this floating around the code? I
know the single-xid cache is potentially vulnerable to xid wraparound
for the same reason.
In response to
pgsql-hackers by date
|Next:||From: Sushant Sinha||Date: 2011-10-25 16:47:25|
|Subject: Re: lexemes in prefix search going through dictionary
|Previous:||From: Alvaro Herrera||Date: 2011-10-25 16:33:23|
|Subject: Re: isolationtester's "dry run" mode|