Re: logical decoding : exceeded maxAllocatedDescs for .spill files
От | Amit Khandekar |
---|---|
Тема | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
Дата | |
Msg-id | CAJ3gD9ecYNGv5PScwjJ-XcY=EngSbWUp7QrD5HwytY-V=QpKxQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: logical decoding : exceeded maxAllocatedDescs for .spill files (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
Список | pgsql-hackers |
On Wed, 20 Nov 2019 at 13:10, Amit Kapila <amit.kapila16@gmail.com> wrote: > See comment in pgunlink() "We need to loop because even though > PostgreSQL uses flags that allow unlink while the file is open, other > applications might have the file > open without those flags.". Can you once see if there is any flag > that you have missed to pass to allow this? > If there is nothing we > can do about it, then we might need to use some different API or maybe > define a new API that can handle this. There were objections against modifying the vfd api only for this replication-related use-case. Having a new API will require all the changes required to enable the virtual FDs feature that we need from vfd. If nothing works out from the FILE_SHARE_DELETE thing, I am thinking, we can use VFD, plus we can keep track of per-subtransaction vfd handles, and do something similar to AtEOSubXact_Files(). -- Thanks, -Amit Khandekar EnterpriseDB Corporation The Postgres Database Company
В списке pgsql-hackers по дате отправления: