Re: [HACKERS] PG_GETARG_GISTENTRY?
От | Noah Misch |
---|---|
Тема | Re: [HACKERS] PG_GETARG_GISTENTRY? |
Дата | |
Msg-id | 20170425011052.GA270877@rfd.leadboat.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] PG_GETARG_GISTENTRY? (Mark Dilger <hornschnorter@gmail.com>) |
Ответы |
[HACKERS] Use PG_DETOAST_DATUM_SLICE in bitlength() (was Re:PG_GETARG_GISTENTRY?)
|
Список | pgsql-hackers |
On Mon, Apr 24, 2017 at 09:25:25AM -0700, Mark Dilger wrote: > Here is a small patch for the next open commitfest which handles a case > that Noah's commits 9d7726c2ba06b932f791f2d0cc5acf73cc0b4dca and > 3a0d473192b2045cbaf997df8437e7762d34f3ba apparently missed. The scope for those commits was wrappers of PG_DETOAST_DATUM_PACKED(), which does not include PG_DETOAST_DATUM_SLICE(). > Noah, if you left this case out intentionally, sorry for the noise. I did not > immediately see any reason not to follow your lead for this function. This is not following my lead, but that doesn't make it bad. It's just a different topic.
В списке pgsql-hackers по дате отправления: