| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changeset Extraction v7.9.1 |
| Date: | 2014-03-17 13:13:38 |
| Message-ID: | CA+TgmoZuBJmqU9dpYa-4RB8KhT5C5ObaJD1sJkTq5nR6cPLuqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 17, 2014 at 8:29 AM, Andres Freund <andres(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-03-17 13:14:51 | Re: Changeset Extraction v7.9.1 |
| Previous Message | Andres Freund | 2014-03-17 12:58:15 | Re: Changeset Extraction v7.9.1 |