Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?
Дата
Msg-id CALj2ACX6SoEY1XxCQcyt1LgqMG+S9aB2sh-ZGQN2Rdu3nzFhUA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Ответы Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Список pgsql-hackers
Дерево обсуждения 
On Wed, May 19, 2021 at 8:28 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> >>> I agree with throwing an error for non-numeric junk though.
> >>> Allowing that on the grounds of backwards compatibility
> >>> seems like too much of a stretch.
> >>
> >> +1.
> >
> > +1.
>
> +1

Thanks all for your inputs. PSA which uses parse_int for
batch_size/fech_size and parse_real for fdw_startup_cost and
fdw_tuple_cost.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS
Следующее
От: Dilip Kumar
Дата:
Сообщение: Re: pg_get_wal_replay_pause_state() should not return 'paused' while a promotion is ongoing.