Re: Sudden database error with COUNT(*) making Query Planner crashes: variable not found in subplan target list

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: Sudden database error with COUNT(*) making Query Planner crashes: variable not found in subplan target list
Дата
Msg-id CAApHDvqFu4S0f4TesWZU8ArjFhu0j4gZZVBEQCNO5rfhzYQ1Sg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Sudden database error with COUNT(*) making Query Planner crashes: variable not found in subplan target list  (David Rowley <dgrowleyml@gmail.com>)
Список pgsql-hackers
On Wed, 8 Jun 2022 at 08:31, David Rowley <dgrowleyml@gmail.com> wrote:
> So it does appear that the location index is being chosen, at least
> with the data that I inserted. Those gist indexes are costing quite a
> bit cheaper than the cheapest btree index.

This seems just to be because the gist indexes are smaller, which is
likely due to me having inserted NULL values into them.

postgres=# select pg_relation_size('logistic_site_key_key');
 pg_relation_size
------------------
            16384
(1 row)


postgres=# select pg_relation_size('logistic_site_location_54ae0166_id');
 pg_relation_size
------------------
             8192
(1 row)

David



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Collation version tracking for macOS
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Collation version tracking for macOS