| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | virgile(dot)crevon(at)dassault-aviation(dot)com |
| Subject: | default_tablespace and parallel queries |
| Date: | 2019-09-26 12:38:24 |
| Message-ID: | 156950150435.1208.13620233301096219314@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/manage-ag-tablespaces.html
Description:
Hi,
"default_tablespace" parameter in "postgresql.conf" does something to
GATHER (in parallel query).
Because when default_tablespace is set to whatever name, and the tablespace
doesn't exist, a query using parallel query is now giving the following
error :
2019-09-25 16:42:50.444 GMT [71530] ERROR: invalid value for parameter
"default_tablespace": "DATA"
2019-09-25 16:42:50.444 GMT [71530] DETAIL: Tablespace "DATA" does not
exist.
So i suggest to add in documentation that this parameter have an effect on
parallel_query.
I will fill in a bug report today for this "side effect".
regards
Virgile
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Bergmaier | 2019-09-26 13:09:03 | Re: BUG #16022: to_json on arrays with unusual lower bound is not intuitive |
| Previous Message | Peter Eisentraut | 2019-09-26 08:53:43 | Re: Do not use C++ style comments (// comments). Strict ANSI C compilers do not accept them. |