mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-09 08:10:09 +08:00
542320c2bd
The previous coding in get_const_expr() tried to avoid quoting integer, float, and numeric literals if at all possible. While that looks nice, it means that dumped expressions might re-parse to something that's semantically equivalent but not the exact same parsetree; for example a FLOAT8 constant would re-parse as a NUMERIC constant with a cast to FLOAT8. Though the result would be the same after constant-folding, this is problematic in certain contexts. In particular, Jeff Davis pointed out that this could cause unexpected failures in ALTER INHERIT operations because of child tables having not-exactly-equivalent CHECK expressions. Therefore, favor correctness over legibility and dump such constants in quotes except in the limited cases where they'll be interpreted as the same type even without any casting. This results in assorted small changes in the regression test outputs, and will affect display of user-defined views and rules similarly. The odds of that causing problems in the field seem non-negligible; given the lack of previous complaints, it seems best not to change this in the back branches. |
||
|---|---|---|
| .. | ||
| bit.out | ||
| bytea.out | ||
| cash.out | ||
| char_1.out | ||
| char.out | ||
| cidr.out | ||
| date.out | ||
| float4.out | ||
| float8.out | ||
| inet.out | ||
| init.out | ||
| int2.out | ||
| int4.out | ||
| int8.out | ||
| interval.out | ||
| macaddr.out | ||
| not_equal.out | ||
| numeric.out | ||
| oid.out | ||
| text_1.out | ||
| text.out | ||
| time.out | ||
| timestamp.out | ||
| timestamptz.out | ||
| timetz.out | ||
| varbit.out | ||
| varchar_1.out | ||
| varchar.out | ||