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.
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
Also, this is the case of first startup of the postgres server.
This msg is shown in the startup logs.
2011/10/10 Harshitha S
> Hi,
>
> The postgres server version is 9.0.4 on the Linux platform.
> The vaccum - related settings have default values.
>
> If it is OID wrap around,
ee
> http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> Especially:
> - server version, platform
> - vacuum-related settings
>
> It *might* be OID wraparaound.
>
>
>
>
> 2011/10/10 Harshitha S
>
>> Hi,
>>
>> We are the following msg in the
Hi,
We are the following msg in the postgres logs.
"could not create file "base/16384/11500": File exists"
Some links indicate that the issue is related to OIDs.
Please help me in understanding why the message is appearing and how the
issue can be resolved.
Regards,
Harshitha
Hi,
I am trying to integrate a tracing framework in the Postgres code.
I need to know if elog.c under backend/utils/error is the place where the
changes can be made.
The tracing framework that I want to integrate has some additional
capability. I want to replace the tracing and logging functional
