pgsql: Doc: back-patch documentation about limitations of CHECK constra

2019-12-11 Thread Tom Lane
Doc: back-patch documentation about limitations of CHECK constraints. Back-patch commits 36d442a25 and 1f66c657f into all supported branches. I'd considered doing this when putting in the latter commit, but failed to pull the trigger. Now that we've had an actual field complaint about the lack o

pgsql: Doc: back-patch documentation about limitations of CHECK constra

2019-12-11 Thread Tom Lane
Doc: back-patch documentation about limitations of CHECK constraints. Back-patch commits 36d442a25 and 1f66c657f into all supported branches. I'd considered doing this when putting in the latter commit, but failed to pull the trigger. Now that we've had an actual field complaint about the lack o

pgsql: Doc: back-patch documentation about limitations of CHECK constra

2019-12-11 Thread Tom Lane
Doc: back-patch documentation about limitations of CHECK constraints. Back-patch commits 36d442a25 and 1f66c657f into all supported branches. I'd considered doing this when putting in the latter commit, but failed to pull the trigger. Now that we've had an actual field complaint about the lack o

pgsql: Doc: back-patch documentation about limitations of CHECK constra

2019-12-11 Thread Tom Lane
Doc: back-patch documentation about limitations of CHECK constraints. Back-patch commits 36d442a25 and 1f66c657f into all supported branches. I'd considered doing this when putting in the latter commit, but failed to pull the trigger. Now that we've had an actual field complaint about the lack o

pgsql: Doc: back-patch documentation about limitations of CHECK constra

2019-12-11 Thread Tom Lane
Doc: back-patch documentation about limitations of CHECK constraints. Back-patch commits 36d442a25 and 1f66c657f into all supported branches. I'd considered doing this when putting in the latter commit, but failed to pull the trigger. Now that we've had an actual field complaint about the lack o