Commit0275ecf

committed

Update FDW docs to reflect existence of CHECK constraints.

Generalize the remarks previously made about NOT NULL constraints toCHECK constraints.Etsuro Fujita

1 parent060a122 commit0275ecfCopy full SHA for 0275ecf

File tree

-7

lines changed

-7

lines changed

Lines changed: 7 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -242,13 +242,13 @@ IterateForeignScan (ForeignScanState *node);`
`242`	`242`
`243`	`243`	`<para>`
`244`	`244`	`Note that <productname>PostgreSQL</productname>'s executor doesn't care`
`245`		`- whether the rows returned violate any<literal>NOT NULL</literal>`
`246`		`-constraints that were defined onthe foreign tablecolumns— but`
`247`		`-the planner does care, and may optimize queries incorrectly if`
`248`		`-<literal>NULL</> values are present in a column declared not to contain`
`249`		`-them. If a <literal>NULL</> value is encountered when the user has`
`250`		`-declared that none should be present, it may be appropriate toraise an`
`251`		`-error (just as you would need to do in the caseof a data type mismatch).`
	`245`	`+ whether the rows returned violate anyconstraints that were defined on`
	`246`	`+ the foreign table — but the planner does care, and may optimize`
	`247`	`+queries incorrectly if there are rows visible in the foreign table that`
	`248`	`+do not satisfy a declared constraint. If a constraint is violated when`
	`249`	`+the user has declared that the constraint should hold true, it may be`
	`250`	`+appropriate to raise an error (just as you would need todo in the case`
	`251`	`+ of a data type mismatch).`
`252`	`252`	`</para>`
`253`	`253`
`254`	`254`	`<para>`

Comments

(0)