Prev: Allow parentheses around the query expression that follows a WITH clause
Next: Make TOAST_TUPLES_PER_PAGE configurable per table.
From: Simon Riggs on 1 Feb 2010 17:32 In the docs it says "It is also possible to tie a session default to a specific database rather than to a role; see ALTER DATABASE. If there is a conflict, database-role-specific settings override role-specific ones, which in turn override database-specific ones." Whereas in process_settings() the sequence is this ApplySetting(databaseid, roleid, relsetting, PGC_S_DATABASE_USER); ApplySetting(InvalidOid, roleid, relsetting, PGC_S_USER); ApplySetting(databaseid, InvalidOid, relsetting, PGC_S_DATABASE); which looks to me like database-role specific settings are overridden by both user and database specific ones, in contrast to how the docs describe this. Am I confused, or is this a problem? Not that bothered, but seems like the docs provide more useful behaviour and the code less useful. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |