forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit9b3900c
committed
Avoid memory size overflow when allocating backend activity buffer
The code in charge of copying the contents of PgBackendStatus to localmemory could fail on memory allocation because of an overflow on theamount of memory to use. The overflow can happen when combining a highvalue track_activity_query_size (max at 1MB) with a largemax_connections, when both multiplied get higher than INT32_MAX as bothparameters treated as signed integers. This could for example triggerwith the following functions, all calling pgstat_read_current_status():- pg_stat_get_backend_subxact()- pg_stat_get_backend_idset()- pg_stat_get_progress_info()- pg_stat_get_activity()- pg_stat_get_db_numbackends()The change to use MemoryContextAllocHuge() has been introduced in8d0ddcc, so backpatch down to 12.Author: Jakub WartakDiscussion:https://postgr.es/m/CAKZiRmw8QSNVw2qNK-dznsatQqz+9DkCquxP0GHbbv1jMkGHMA@mail.gmail.comBackpatch-through: 121 parent22b2e6e commit9b3900c
1 file changed
+2
-1
lines changedLines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3394 | 3394 | | |
3395 | 3395 | | |
3396 | 3396 | | |
3397 | | - | |
| 3397 | + | |
| 3398 | + | |
3398 | 3399 | | |
3399 | 3400 | | |
3400 | 3401 | | |
| |||
0 commit comments
Comments
(0)