On 09/04/2012 02:15 PM, Harshitha S wrote:
Hi,
Can Latch - that postgres already uses, be used to achieve the same?
With a quick look at latches I'm not sure what that'd have to do with
file change notification.
Magnus's suggestion to use a signal - especially as one is already
understood
On Mon, Sep 3, 2012 at 8:30 AM, 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.
>
> This is to reduce the 3-
Hi,
Can Latch - that postgres already uses, be used to achieve the same?
On Tue, Sep 4, 2012 at 6:31 AM, Craig Ringer wrote:
> 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 cr
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 portab
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 portab
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.
This is to reduce the 3-4 seconds delay that exists with the current
implementation in p
