Re: pageinspect's infomask and infomask2 as smallint

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: pageinspect's infomask and infomask2 as smallint
Дата
Msg-id 4D5A3B8D.9000401@enterprisedb.com
обсуждение исходный текст
Ответ на pageinspect's infomask and infomask2 as smallint  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: pageinspect's infomask and infomask2 as smallint  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 14.02.2011 21:49, Alvaro Herrera wrote:
> Thanks to Noah Misch's review of the keylock patch I noticed that
> pageinspect's heap_page_items(bytea) function returns infomask and
> infomask2 as smallint (signed).  But the fields in the tuple header are
> 16 bits unsigned, so if the high (16th) bit is set, it returns negative
> values which seem hard to handle.  Not a problem for infomask, because
> the high bit is used for a VACUUM FULL-era flag; but in infomask2 it is
> used.
>
> This seems hard to fix for existing installations with the unpackaged
> module already loaded -- IIRC it's not acceptable to drop a function,
> which is what would need to be done here.

pageinspect is just a debugging aid, so I think we should change it from 
smallint to int4 in 9.1, and not bother backporting.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Itagaki Takahiro
Дата:
Сообщение: Re: CommitFest 2011-01 as of 2011-02-04
Следующее
От: Jan Urbański
Дата:
Сообщение: Re: pl/python do not delete function arguments