Re: stopping access to a database

So,
	the connections that will see the new data won't be able to access data until that 
transaction has finished the 'commit' stage, or will they be able to read some of the records 
while the importation is partially done?

1/28/2003 9:27:59 AM, Charles Tassell  wrote:

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