Re: Way to shutdown/freeze/stop an individual database without taking postmaster down?

From: Ben <bench(at)silentmedia(dot)com>
To: W S <ws3reg(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Way to shutdown/freeze/stop an individual database without taking postmaster down?
Date: 2008-04-10 18:36:34
Message-ID: Pine.LNX.4.64.0804101136040.18595@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

What do you hope to get out of this that you wouldn't get out of locking
out access?

On Thu, 10 Apr 2008, W S wrote:

> Greetings,
>
> I was asked this question, and I wasn't sure if it is possible:
>
>
> do you know of a way to stop just one database (not delete/drop) on
> our PostgreSQL 8.1 server?
>
>
> And, while I know how to shut down postmaster, and/or put in rules to
> pg_hba.conf to limit access to a certain database, is there any way to
> freeze or stop just one database and not others? I'm attempting to
> RTFM it, but so far I've had no luck.
>
> Thanks,
> Will
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sam Mason 2008-04-10 18:38:00 Re: percentile rank query
Previous Message Douglas McNaught 2008-04-10 18:34:58 Re: how to use postgre sql from inside process