Skip site navigation (1) Skip section navigation (2)

Re: Blocking access to the database??

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Carlos Oliva <carlos(at)pbsinet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Blocking access to the database??
Date: 2003-05-29 18:39:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Please keep this on the list. Especially if you are asking followup
questions as other people may be better placed to help you.

On Thu, May 29, 2003 at 13:49:31 -0400,
  Carlos Oliva <carlos(at)pbsinet(dot)com> wrote:
> If I had to reorganize the database, I would prefer to terminate the
> connections.  Any way to do that without having to restart the db
> server?  Could I kill the PID's for the users (Linux RedHat)
> In order to modify a user's permissions, must I restart the db server?

I am not sure what the answer is to your first two questions.

> Can one do an SQL-dump while users are modifying the data?


> -----Original Message-----
> From: Bruno Wolff III [mailto:bruno(at)wolff(dot)to] 
> Sent: Thursday, May 29, 2003 1:28 PM
> To: Carlos
> Cc: 'pgsql-general(at)postgresql(dot)org'
> Subject: Re: [GENERAL] Blocking access to the database??
> On Thu, May 29, 2003 at 12:29:16 -0400,
>   Carlos <Carlos(at)pbsinet(dot)com> wrote:
> > Hi Forum,
> > 
> > Is there a way to block access to the database or terminate ongoing 
> > connections while I carry-out updates or backups?
> > 
> > Thanks in advance for your reply
> You could update pg_hba.conf and restart the database server.
> Are you sure you want to do that though? You can do consistant backups
> while the database is being updated by other people. And people will see
> a consistant view of the database if you do your updates properly.

pgsql-general by date

Next:From: Carlos OlivaDate: 2003-05-29 18:41:37
Subject: FW: Blocking access to the database??
Previous:From: Jeff EckermannDate: 2003-05-29 18:31:43
Subject: Re: exporting join results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group