Re: Bad Estimate for multi tenant database queries

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: Bad Estimate for multi tenant database queries
Дата
Msg-id CAHOFxGoUNnvKAdnwjMmesLu+RkoMBtkDn+LiPrfewSYP40KCSw@mail.gmail.com
обсуждение исходный текст
Ответ на Bad Estimate for multi tenant database queries  (Peter Grman <peter.grman@gmail.com>)
Ответы Re: Bad Estimate for multi tenant database queries
Список pgsql-general
Дерево обсуждения
CREATE STATISTICS MT_ReservationDepartureUtc (ndistinct) on "AccountCode", "DepartureUtc" from "Reservation"."Reservation";
CREATE STATISTICS MT_ReservationArrivalUtc (ndistinct) on "AccountCode", "ArrivalUtc" from "Reservation"."Reservation";
CREATE STATISTICS MT_ReservationNoShowFeeId (ndistinct) on "AccountCode", "NoShowFeeId" from "Reservation"."Reservation";
CREATE STATISTICS MT_ReservationTimeSliceDefinitionId (ndistinct) on "AccountCode", "TimeSliceDefinitionId" from "Reservation"."Reservation";

but that didn't help either

Did you try with 'dependencies' for the statistics_kind or only ndistinct? What was default_statistics_target set to at the time you created the extended statistics? I am not sure if that value is used, but I would assume so.

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

Предыдущее
От: Nagendra Bandi
Дата:
Сообщение: Re: Postgres HA issue - Standby server does not start after Mastercompute host is shut down
Следующее
От: Michael Lewis
Дата:
Сообщение: Re: literal vs dynamic partition constraint in plan execution