Commit52f436b

committed

Improve documentation about the relationship of extensions and schemas.

There's been some confusion expressed about this point, so clarify.Extended version of a patch by David Wheeler.

1 parente3f719c commit52f436bCopy full SHA for 52f436b

File tree

+12

-0

lines changed

+12

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -359,6 +359,12 @@`
`359`	`359`	`extension.) Also notice that while a table can be a member of an`
`360`	`360`	`extension, its subsidiary objects such as indexes are not directly`
`361`	`361`	`considered members of the extension.`
	`362`	`+ Another important point is that schemas can belong to extensions, but not`
	`363`	`+ vice versa: an extension as such has an unqualified name and does not`
	`364`	`+ exist <quote>within</> any schema. The extension's member objects,`
	`365`	`+ however, will belong to schemas whenever appropriate for their object`
	`366`	`+ types. It may or may not be appropriate for an extension to own the`
	`367`	`+ schema(s) its member objects are within.`
`362`	`368`	`</para>`
`363`	`369`
`364`	`370`	`<sect2>`

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -94,6 +94,12 @@ CREATE EXTENSION [ IF NOT EXISTS ] <replaceable class="parameter">extension_name`
`94`	`94`	`If not specified, and the extension's control file does not specify a`
`95`	`95`	`schema either, the current default object creation schema is used.`
`96`	`96`	`</para>`
	`97`	`+ <para>`
	`98`	`+ Remember that the extension itself is not considered to be within any`
	`99`	`+ schema: extensions have unqualified names that must be unique`
	`100`	`+ database-wide. But objects belonging to the extension can be within`
	`101`	`+ schemas.`
	`102`	`+ </para>`
`97`	`103`	`</listitem>`
`98`	`104`	`</varlistentry>`
`99`	`105`

Comments

(0)