Re: stopping access to a database

From: "codeWarrior" <GPatnude(at)adelphia(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: stopping access to a database
Date: 2003-01-29 06:46:32
Message-ID: b17sum$2slo$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dennis:

You gotta ask yourself -- "how long is the delete / insert going to take
???" -- all of about 3 seconds probably....

I'd just do it in a transaction because you said that database 2 is
"publicly accessible"... What happens if Joe Public is trying to get some of
that public info and you have the systemn locked...

"Dennis Gearon" <gearond(at)cvc(dot)net> wrote in message
news:PL54ZWTRID64QP95PKD952WTXWQLRLRM(dot)3e36b4bb(at)cal-lab(dot)(dot)(dot)
> 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

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar<shridhar_daithankar@persistent.co.in> 2003-01-29 06:54:56 Re: Help with I/O statistics
Previous Message Stephan Szabo 2003-01-29 06:39:57 Re: need much better query perfomance