From: | brian <brian(at)zijn-digital(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tables dissapearing |
Date: | 2007-08-27 23:23:08 |
Message-ID: | 46D35CDC.2010108@zijn-digital.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kamil Srot wrote:
> brian wrote:
>>
>> IMHO, it's not at all improbable, given that this software is
>> connecting to the same databases you are seeing affected by this
>> phenomenon. Not to mention that it's proprietary, so fewer eyes
>> have gone over it.[1] I suggested earlier grepping for 'drop' in
>> your application. Perhaps you should do the same on the CMS.
>>
>> [1] Not meant as a dig at non-free software.
>
> Understood and I agree. I would accept the possibility to do the most
> stupid coding error in the world, but there is simply no statement
> manipulating with the schema in the whole project. To be sure, I
> searched thru the sources for /drop/i and didn't found anywhere but
> the pear framework of PHP (some constants and test patterns of user
> statements)... OK, I agree this can be run by some coincidence and so
> I have started to log all statements in the logfile... but still I
> doubt executing the drop statement is the problem...
Just wondering: what's the name of this table? What's its function? I
think you mentioned that it's pretty well static. But what is it
holding? Maybe that'll provide a clue as to where to look.
brian
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-27 23:28:52 | Re: Detecting whether a point is in a box. |
Previous Message | Kamil Srot | 2007-08-27 23:19:31 | Re: Tables dissapearing |