From: | Jeff Amiel <jamiel(at)istreamimaging(dot)com> |
---|---|
To: | Kamil Srot <kamil(dot)srot(at)nlogy(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tables dissapearing |
Date: | 2007-08-28 14:30:01 |
Message-ID: | 46D43169.9080100@istreamimaging.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My entire shop has set up a betting pool on the outcome of this...so I
hope you post results regardless of the outcome, Kamil.
(in all seriousness, we hope you find/fix the problem before things get
really ugly)
Kamil Srot wrote:
> Richard Huxton wrote:
>> Kamil Srot wrote:
>>> In the version used on this particular server, there is no
>>> automatic/programing way of changing
>>> the schema. Upgrades are done manually and application itself
>>> doesn't need schema changes
>>> for routine operations...
>>
>> In that case, you can settle the matter by making sure your
>> application connects as a user that doesn't own any of the tables.
>> That way they can't be dropped.
>>
> Yes, I'll do it in the future, but now, I want to know what is the
> problem and solve it rather than doing some workarounds (even if they
> are good also from the principle indeed).
>
> Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2007-08-28 14:33:27 | Re: [HACKERS] Undetected corruption of table files |
Previous Message | Bill Moran | 2007-08-28 14:21:02 | Re: Bigtime scaling of Postgresql (cluster and stuff I suppose) |