| From: | Kamil Srot <kamil(dot)srot(at)nlogy(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Erik Jones <erik(at)myemma(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Tables dissapearing |
| Date: | 2007-08-28 07:06:58 |
| Message-ID: | 46D3C992.9060409@nlogy.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Erik Jones <erik(at)myemma(dot)com> writes:
>
>> Also, I'd write a simple "ping" script to check for the table that
>> runs every 5 seconds or so.
>>
>
> I had gathered that the table was being touched constantly by his app,
> so that it'd be immediately obvious when it had gone away. If that's
> not so, then definitely do the above.
>
>
You're right, Tom... the table is intensivelly used in the application
and the application itself
is under not high, but big enough load to buy a hit at least each few
seconds...
If anything happen with the table, entries with not existing relation
will appear in the log
right away.
Regards,
--
Kamil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sanjay | 2007-08-28 07:08:18 | Creating indices on foreign keys |
| Previous Message | Sanjay | 2007-08-28 07:04:07 | Re: EXPLAIN ANALYZE not considering primary and unique indices! |