Re: Tables dissapearing

From: Kamil Srot <kamil(dot)srot(at)nlogy(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Adrian Klaver <aklaver(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Erik Jones <erik(at)myemma(dot)com>
Subject: Re: Tables dissapearing
Date: 2007-08-28 08:29:17
Message-ID: 46D3DCDD.5040106@nlogy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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,
--
Kamil

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Harald Armin Massa 2007-08-28 11:18:36 Re: PostgreSQL vs Firebird feature comparison finished
Previous Message Patryk Kordylewski 2007-08-28 08:28:14 ERROR: table row type and query-specified row type do not match