Re: stopping access to a database

From: Charles Tassell <ctassell(at)isn(dot)net>
To: gearond(at)cvc(dot)net
Cc: postgres list <pgsql-general(at)postgresql(dot)org>
Subject: Re: stopping access to a database
Date: 2003-01-28 17:27:59
Message-ID: 1043774879.5917.22.camel@pinky
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

There is no need to block all access, simply use a transaction. IE:

begin work;
delete from table1;
delete from tabl2;
... so on ..
.. import data ...
commit work;

Anyone who connects while the delete/import is taking place will simply
see the old data, when you run the commit work command, all the new
queries will see the newly imported data.

On Tue, 2003-01-28 at 12:50, Dennis Gearon wrote:
> I configuring 2 databases:
>
> 1/ One be on a https server, and all important data will be encrypted. The only use this
> database will see are:
> A/ Updates 2-3 times a day, max.
> B/ Exporting a smaller set of 'unnormalized' tables for the database below.
> 2/ A publically accessible, (through PHP applications), database that has less secure data
> on it and is not encrypted.
>
> I would like to stop accesses to database 2, delete all records in the 2-4 tables, and reimport
> new records. How would I do this as a user on the system, not as an admin?
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vivek Khera 2003-01-28 17:31:15 Re: ERROR: No one parent tuple was found
Previous Message Bruno Wolff III 2003-01-28 17:08:42 Re: Ref to last INSERT on a table without OIDs?