On Wed, Sep 14, 2016 at 3:54 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
>> I do think this comment is confusing:
>> + *        This value is not locked by the transaction, so this value may
>> + *        be changed while a SELECT that has used these values for planning
>> + *        is still executing.
>> I don't know what it means for "this value" to be locked, or not
>> locked, by the transaction.  Basically, I have no idea what this is
>> trying to explain.
> You're quoting that without context from the line above, which is
> "get_tablespace_io_concurrency"

Sure, but it doesn't make any sense to talk about
tablespace_io_concurrency being locked by a transaction.  At least not
that I can see.

Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to