Re: Potential stack overflow in incremental base backup
| От | Robert Haas |
|---|---|
| Тема | Re: Potential stack overflow in incremental base backup |
| Дата | |
| Msg-id | CA+Tgmoa1C9ZPT+o79AVOKOsqwQmPYL-p8etn+kAD1MUsM+4XDQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Potential stack overflow in incremental base backup (Thomas Munro <thomas.munro@gmail.com>) |
| Ответы |
Re: Potential stack overflow in incremental base backup
|
| Список | pgsql-hackers |
On Wed, Apr 10, 2024 at 6:21 AM Thomas Munro <thomas.munro@gmail.com> wrote: > Could we just write the blocks directly into the output array, and > then transpose them directly in place if start_blkno > 0? See > attached. I may be missing something, but the only downside I can > think of is that the output array is still clobbered even if we decide > to return BACK_UP_FILE_FULLY because of the 90% rule, but that just > requires a warning in the comment at the top. Yeah. This approach makes the name "relative_block_numbers" a bit confusing, but not running out of memory is nice, too. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: