Re: Tables dissapearing

From: Richard Huxton <dev(at)archonet(dot)com>
To: Kamil Srot <kamil(dot)srot(at)nlogy(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:03:12
Message-ID: 46D3D6C0.4000606@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-08-28 08:04:31 Re: Tables dissapearing
Previous Message Ow Mun Heng 2007-08-28 07:41:45 Re: delete vs insert vs update due to primary key dups -> which is better