Re: Changeset Extraction v7.9.1
От | Robert Haas |
---|---|
Тема | Re: Changeset Extraction v7.9.1 |
Дата | |
Msg-id | CA+TgmoZuBJmqU9dpYa-4RB8KhT5C5ObaJD1sJkTq5nR6cPLuqw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Changeset Extraction v7.9.1 (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: Changeset Extraction v7.9.1
|
Список | pgsql-hackers |
On Mon, Mar 17, 2014 at 8:29 AM, Andres Freund <andres@2ndquadrant.com> wrote: >> Perhaps there could be a switch for an fsync interval, or something >> like that. The default could be, say, to fsync every 10 seconds. And >> if you want to change it, then go ahead; 0 disables. Writing to >> standard output would be documented as unreliable. Other ideas >> welcome. > > Hm. That'll be a bit nasty. fsync() is async signal safe, but it's still > forbidden to be called from a signal on windows IIRC. I guess we can > couple it with the standby_message_timeout stuff. Eh... I don't see any need to involve signals. I'd just check after each write() whether enough time has passed, or something like that. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: