Re: potential stuck lock in SaveSlotToPath()
| От | Robert Haas |
|---|---|
| Тема | Re: potential stuck lock in SaveSlotToPath() |
| Дата | |
| Msg-id | CA+TgmobPKGJs83ss-QumHQNNfkPMSORKz8ZVHaNDkdAb=-qedw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: potential stuck lock in SaveSlotToPath() (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: potential stuck lock in SaveSlotToPath()
|
| Список | pgsql-hackers |
On Wed, Mar 18, 2020 at 4:25 PM Andres Freund <andres@anarazel.de> wrote: > I don't see a valid reason for that though - if anything it's dangerous, > because we're not persistently saving the slot. It should fail the > checkpoint imo. Robert, do you have an idea? Well, the comment atop SaveSlotToPath says: * This needn't actually be part of a checkpoint, but it's a convenient * location. And I agree with that. Incidentally, the wait-event handling in SaveSlotToPath() doesn't look right for the early-exit cases either. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: