Might be worth mentioning that temp_tablespaces can contain duplicate values

Started by Nonamealmost 10 years ago2 messagesdocs
Jump to latest
#1Noname
alecz@berkeley.edu

The following documentation comment has been logged on the website:

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 with duplicate entries and have found
that it keeps those duplicates, making that entry used more frequently. This
is useful if the user wants to use one tablespace more frequently than
others. Example: "tablespace1, tablespace1, tablespace2" It'll pick
tablespace1 about 2X as often as tablespace2.

Support for duplicate values isn't explicitly mentioned in the
documentation, but I inferred it from the wording about the parameter being
a "list." But I had to go test to make sure it would work as I thought.

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

#2Peter Eisentraut
peter_e@gmx.net
In reply to: Noname (#1)
Re: Might be worth mentioning that temp_tablespaces can contain duplicate values

On 7/5/16 9:43 PM, alecz@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 with duplicate entries and have found
that it keeps those duplicates, making that entry used more frequently. This
is useful if the user wants to use one tablespace more frequently than
others. Example: "tablespace1, tablespace1, tablespace2" It'll pick
tablespace1 about 2X as often as tablespace2.

Support for duplicate values isn't explicitly mentioned in the
documentation, but I inferred it from the wording about the parameter being
a "list." But I had to go test to make sure it would work as I thought.

Anyone have concerns about explicitly documenting this behavior? Seems
possibly useful to me.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs