Re: "parallel= " information is not coming in pg_dumpall for create aggregate

Поиск
Список
Период
Сортировка
От Fabrízio de Royes Mello
Тема Re: "parallel= " information is not coming in pg_dumpall for create aggregate
Дата
Msg-id CAFcNs+p0yJsXauPewrXSEP4T0D18UHT3=J=UoATR9uGdrCze1Q@mail.gmail.com
обсуждение исходный текст
Ответ на "parallel= " information is not coming in pg_dumpall for create aggregate  (tushar <tushar.ahuja@enterprisedb.com>)
Ответы Re: "parallel= " information is not coming in pg_dumpall for create aggregate  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers

On Mon, Apr 18, 2016 at 5:30 AM, tushar <tushar.ahuja@enterprisedb.com> wrote:
>
>
> Hi,
>
> I checked in PG 9.6 , if we create an aggregate function with saying - parallel=safe/restricted/unsafe and then take
> a pg_dumpall of the entire cluster , "parallel= " is missing from create aggregate syntax
>
> Steps to reproduce -
>
> .)connect to psql terminal and create an aggregate function
>
> postgres=# CREATE AGGREGATE unsafe_sum100 (float8)
> (
>     stype = float8,
>     sfunc = float8pl,
>     mstype = float8,
>     msfunc = float8pl,
>     minvfunc = float8mi,
>     parallel=safe);
> CREATE AGGREGATE
>
> .)perform pg_dumpall against that cluster
>
> .)check the content of create aggregate unsafe_sum100 in the file
>
> "
> -
> -- Name: unsafe_sum100(double precision); Type: AGGREGATE; Schema: public; Owner: centos
> --
>
> CREATE AGGREGATE unsafe_sum100(double precision) (
>     SFUNC = float8pl,
>     STYPE = double precision,
>     MSFUNC = float8pl,
>     MINVFUNC = float8mi,
>     MSTYPE = double precision
> );
>
> "

You're correct... try the attached patch to fix it.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello
Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Memory leak in GIN index build
Следующее
От: Teodor Sigaev
Дата:
Сообщение: Re: GIN data corruption bug(s) in 9.6devel