diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2024-03-17 12:19:30 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2024-03-17 12:30:51 +0100 |
| commit | d939cb2fd612acde0304913213cfbdb01994e682 (patch) | |
| tree | dacc70fa1b94cc377245ff9f14c7166745e5939f /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 012460ee93c304fbc7220e5b55d9d0577fc766ab (diff) | |
| download | postgresql-d939cb2fd612acde0304913213cfbdb01994e682.tar.gz postgresql-d939cb2fd612acde0304913213cfbdb01994e682.zip | |
Generalize handling of nullable pg_attribute columns in DDL
DDL code uses tuple descriptors to pass around pg_attribute values
during table and index creation. But tuple descriptors don't include
the variable-length/nullable columns of pg_attribute, so they have to
be handled separately. Right now, the attoptions field is handled in
a one-off way with a separate argument passed to
InsertPgAttributeTuples(). The other affected fields of pg_attribute
are right now not needed at relation creation time.
The goal of this patch is to generalize this to allow handling
additional variable-length/nullable columns of pg_attribute in a
similar manner. For that, create a new struct
FormExtraData_pg_attribute, which is to be passed around in parallel
to the tuple descriptor and optionally supplies the additional
columns. Right now, this struct only contains one field for
attoptions, so no functionality is actually changed by this.
Reviewed-by: Tomas Vondra <tomas.vondra@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/flat/4da8d211-d54d-44b9-9847-f2a9f1184c76@eisentraut.org
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions