diff options
| author | Michael Paquier <michael@paquier.xyz> | 2020-11-19 10:36:08 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2020-11-19 10:36:08 +0900 |
| commit | 13b58f8934e6252868231c3493d49b8c2b363e5d (patch) | |
| tree | 96b3bc53cc0b222e251f370997c74a9124ca0b82 /src/backend/parser/parse_expr.c | |
| parent | 27838981be9de35d54ffcdc6cc06b5d5ea9e0cee (diff) | |
| download | postgresql-13b58f8934e6252868231c3493d49b8c2b363e5d.tar.gz postgresql-13b58f8934e6252868231c3493d49b8c2b363e5d.zip | |
Improve failure detection with array parsing in pg_dump
Similarly to 3636efa, the checks done in pg_dump when parsing array
values from catalogs have been too lax. Under memory pressure, it could
be possible, though very unlikely, to finish with dumps that miss some
data like:
- Statistics for indexes
- Run-time configuration of functions
- Configuration of extensions
- Publication list for a subscription
No backpatch is done as this is not going to be a problem in practice.
For example, if an OOM causes an array parsing to fail, a follow-up code
path of pg_dump would most likely complain with an allocation failure
due to the memory pressure.
Author: Michael Paquier
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/20201111061319.GE2276@paquier.xyz
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions