Re: [HACKERS] [sqlsmith] Planner crash on foreign table join

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] [sqlsmith] Planner crash on foreign table join
Дата
Msg-id CA+TgmoY-uLO=eZA8A2OqWfPOYKjkPQnLYi4DQ0O5q=o+Nr_Z9w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] [sqlsmith] Planner crash on foreign table join  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] [sqlsmith] Planner crash on foreign table join
Список pgsql-hackers
On Sat, Apr 8, 2017 at 3:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This makes me wonder whether we were being penny-wise and pound-foolish
> by not making Bitmapsets be a kind of Node, so that there could be IsA
> assertions in the bitmapset.c routines, as there are for Lists.  Most
> Bitmapsets in a typical backend probably have only one payload word
> (ie highest member < 32), so right now they occupy 8 bytes.  Adding
> a nodetag would kick them up to the next palloc category, 16 bytes,
> which is probably why I didn't do it like that to begin with.
> Still, that decision is looking unduly byte-miserly in 2017.

I think it's pretty dubious to change this, honestly.  Just because it
would have caught this one bug doesn't make it an especially valuable
thing in general.  Bytes are still not free.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: [HACKERS] pgbench - allow to store select results intovariables
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] [sqlsmith] Planner crash on foreign table join