Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags
Дата
Msg-id d1f28eb6-f8b5-387e-39e5-1cc3e3092974@BlueTreble.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags  ("Seki, Eiji" <seki.eiji@jp.fujitsu.com>)
Ответы Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags  ("Seki, Eiji" <seki.eiji@jp.fujitsu.com>)
Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags  ("Seki, Eiji" <seki.eiji@jp.fujitsu.com>)
Re: [HACKERS] Proposal: GetOldestXminExtend for ignoring arbitraryvacuum flags  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 2/14/17 3:13 AM, Seki, Eiji wrote:
>   +extern TransactionId GetOldestXmin(Relation rel, uint8 ignoreFlags);

My impression is that most other places that do this sort of thing just 
call the argument 'flags', so as not to "lock in" a single idea of what 
the flags are for. I can't readily think of another use for flags in 
GetOldestXmin, but ISTM it's better to just go with "flags" instead of 
"ignoreFlags".
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: [HACKERS] possibility to specify template database for pg_regress
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting for checkpoint