diff options
| author | Andres Freund <andres@anarazel.de> | 2015-02-21 22:25:49 +0100 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2015-02-21 22:31:54 +0100 |
| commit | eb68379c38202180bc8e33fb9987284e314b7fc8 (patch) | |
| tree | 0e6dcc59b1fabfe9c63b0d0377607acee7dad025 /src/backend/utils/adt/arrayfuncs.c | |
| parent | 0627eff3602c0ce0e8358d48ddb3ffa73963e4d0 (diff) | |
| download | postgresql-eb68379c38202180bc8e33fb9987284e314b7fc8.tar.gz postgresql-eb68379c38202180bc8e33fb9987284e314b7fc8.zip | |
Allow forcing nullness of columns during bootstrap.
Bootstrap determines whether a column is null based on simple builtin
rules. Those work surprisingly well, but nonetheless a few existing
columns aren't set correctly. Additionally there is at least one patch
sent to hackers where forcing the nullness of a column would be helpful.
The boostrap format has gained FORCE [NOT] NULL for this, which will be
emitted by genbki.pl when BKI_FORCE_(NOT_)?NULL is specified for a
column in a catalog header.
This patch doesn't change the marking of any existing columns.
Discussion: 20150215170014.GE15326@awork2.anarazel.de
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions