Hi
As shown below, the argument types of autovacuum_vacuum_insert_scale_factor and
toast.autovacuum_vacuum_insert_scale_factor are different from the others.
---
autovacuum_vacuum_scale_factor, toast.autovacuum_vacuum_scale_factor (floating
point)
autovacuum_vacuum_insert_scale_factor,
toast.au
>- extensions
>+ extensions (enum)
>
>Since each value in "extensions" parameter is not limitted like
>shared_preload_libraries, its type should be "string"?
Yes, I fixed it.
>
>- fdw_startup_cost
>+ fdw_startup_cost (double
>+ precision)
>- fdw_tuple_cost
>+ fdw_tuple_cost
Hi,
I add argument type to postgres-fdw parameters in postgres-fdw.sgml.
I think this change is kind. Do you think?
Regards,
Shinya Kato
add_argument_type_to_postgres-fdw_docs.patch
Description: add_argument_type_to_postgres-fdw_docs.patch
> Hi,
>
> The index items for pg_stat_progress_xxx views point to the
> "Viewing Statistics" section, but not to the dedicated section
> (e.g., "ANALYZE Progress
> Reporting") for each view. IMO this is very inconvenient when
> finding the section describing each pg_stat
>>> Hi,
>>>
>>> The index items for pg_stat_progress_xxx views point to the "Viewing
>>> Statistics" section, but not to the dedicated section (e.g., "ANALYZE
>>> Progress
>>> Reporting") for each view. IMO this is very inconvenient when finding
>>> the section describing each pg_stat_progress_xxx
> Hi,
>
> The index items for pg_stat_progress_xxx views point to the "Viewing
> Statistics" section, but not to the dedicated section (e.g., "ANALYZE
> Progress
> Reporting") for each view. IMO this is very inconvenient when finding
> the section describing each pg_stat_progress_xxx view, from
