Re: What is an item pointer, anyway?

Поиск
Список
Период
Сортировка
Искать
От
Peter Geoghegan
Тема
Re: What is an item pointer, anyway?
Дата
Msg-id
CAH2-WzmPZC2HAXj5jiyhP-Z5tr0OD_ThcMyTy1pSaL-HtdZ15Q@mail.gmail.com
Ответ на
Список
Дерево обсуждения
What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Ashwin Agrawal <aagrawal@pivotal.io>
Re: What is an item pointer, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
Re: What is an item pointer, anyway? Peter Geoghegan <pg@bowt.ie>
On Fri, Apr 26, 2019 at 5:05 PM Tom Lane  wrote:
> Yeah, I'd be fine with that, although the disconnect between the type
> name and the comment terminology might confuse some people.

Maybe, but the fact that the ItemIdData struct consists of bit fields
that are all named "lp_*" offers a hint. Plus you have the LP_*
constants that get stored in ItemIdData.lp_flags.

I wouldn't call the struct ItemIdData if I was in a green field
situation, but it doesn't seem too bad under the present
circumstances. I'd rather not change the struct's name, because that
would probably cause problems without any real benefit. OTOH, calling
two closely related but distinct things by the same name is atrocious.

-- 
Peter Geoghegan


В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата:
От: Michael Paquier
Дата:
FAQ