Hello all
The postgreSQL version is needed internally in order to make the code work
because for example the type of funcctx->max_calls changed on 9.6
uint64_t result_count = 0;
...
#if PGSQL_VERSION > 95
funcctx->max_calls = result_count;
#else
funcctx->max_calls = (uint
Thanks,
> It is not safe due views - that are saved in post analyze form.
What is post analyze form? any link that you can give me to read about it?
Thanks
De: Pavel Stehule
Enviado: lunes, 3 de abril de 2017 11:21 p. m.
Para: Vicky Vergara
Cc: pg
Enviado: lunes, 3 de abril de 2017 11:28 p. m.
Para: Vicky Vergara
Cc: pgsql-hackers@postgresql.org
Asunto: Re: [HACKERS] Instead of DROP function use UPDATE pg_proc in an upgrade
extension script
>>>>> "Vicky" == Vicky Vergara writes:
Vicky> UPDATE pg_proc SET [...]
nd
of other objects do I need to test besides views.
My plan, is to use the second method:
- when the current names of the OUT parameters don't change, and there is an
additional OUT parameter
- when the current names of the IN parameters don't change, and there is an
additional IN parameter with a default value
Thanks
Vicky Vergara
gnostic pop
#endif
Vicky
____
De: Tom Lane
Enviado: viernes, 12 de febrero de 2016 01:45 p. m.
Para: Vicky Vergara
Cc: pgsql-hackers@postgresql.org
Asunto: Re: [HACKERS] Compilation warning on 9.5
Vicky Vergara writes:
> I wonder if -std=gnu99 is the correct stan
1 to 9.4)
Note1: when pgRouting gets released, all those flags:
-Wall -Wconversion -pedantic -fmax-errors=10 -Wmissing-prototypes
will be removed, and of course those warnings won't show up.
Thanks
Vicky Vergara
