Re: Range Types - typo + NULL string constructor
От | Jeff Davis |
---|---|
Тема | Re: Range Types - typo + NULL string constructor |
Дата | |
Msg-id | 1319560632.27819.16.camel@jdavis обсуждение исходный текст |
Ответ на | Re: Range Types - typo + NULL string constructor (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Range Types - typo + NULL string constructor
Re: Range Types - typo + NULL string constructor |
Список | pgsql-hackers |
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. Regards,Jeff Davis
В списке pgsql-hackers по дате отправления: