On 8/2/16 1:31 PM, Alvaro Herrera wrote:
> I think it's easier to dodge the rules topic entirely here and just
> mention statement triggers. Using rules you cannot cover the truncate
> case, for instance.
done
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development,
On 5/31/15 7:25 PM, Clément Prévost wrote:
> I attached 2 patches: 1 to fix erroneous documentation and the other to
> fix information schema types.
I have fixed these two.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & S
On 5/31/15 8:27 PM, Clément Prévost wrote:
> Here is another patch to fix the name of the column
> information_schema.routines.result_cast_char_set_name that was
> mistakenly named result_cast_character_set_name.
This one is actually named result_cast_character_set_name in the
standard, although t
On 7/5/16 9:43 PM, al...@berkeley.edu wrote:
> Page: https://www.postgresql.org/docs/9.5/static/runtime-config-client.html
> Description:
>
> The section on temp_tablespaces is here:
> https://www.postgresql.org/docs/9.5/static/runtime-config-client.html
>
> I've tried setting temp_tablespaces wi
Peter Eisentraut writes:
> On 5/31/15 8:27 PM, Clément Prévost wrote:
>> Here is another patch to fix the name of the column
>> information_schema.routines.result_cast_char_set_name that was
>> mistakenly named result_cast_character_set_name.
> This one is actually named result_cast_character_s
