From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Harshitha S <hershetha(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Reduce the time to know trigger_file's existence |
Date: | 2012-09-04 00:58:21 |
Message-ID: | 5045522D.3060501@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 09/03/2012 04:30 PM, Harshitha S wrote:
> Hi,
> We are trying to introduce a thread that monitors the creation of the
> trigger_file. As and when the file is created, the process that monitors
> postgres server needs to be notified through the inotify API.
File system notification APIs aren't portable. If you want to implement
this you'll need to support at least the Windows FSNotify stuff,
notification features compatible with several different Linux versions
and with the BSDs, with a fallback to polling for other platforms.
For Windows:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365261(v=vs.85).aspx
This will mean adding a new internal API and then adding backend/port/
implementations for various platforms, as well as taking the current
code and splitting it out into a port file that gets used if no other is
chosen.
This page is likely to be useful:
http://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-09-04 01:01:41 | Re: Reduce the time to know trigger_file's existence |
Previous Message | Gavin Flower | 2012-09-03 22:45:49 | Re: "Too far out of the mainstream" |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-09-04 01:01:41 | Re: Reduce the time to know trigger_file's existence |
Previous Message | Heikki Linnakangas | 2012-09-04 00:40:22 | Re: Cascading replication and recovery_target_timeline='latest' |