From: | postgre(at)seznam(dot)cz |
---|---|
To: | paul rivers <privers(at)berkeley(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERAL] close database, nomount state |
Date: | 2008-05-05 17:38:18 |
Message-ID: | 1058.1480-28870-1538816510-1210009098@seznam.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
paul rivers <privers(at)berkeley(dot)edu> wrote:
> Short answer-- no.
>
> Longer answer-- there's really no need for the Oracle-esque nomount
> state in Pg. If you're doing media recovery, it's very much all or
> nothing, cluster-wide. You are not going to do media recovery for a set
> of tablespaces, for example. If you'd like to drop a database, you can
> cut off connections (say, via pg_hba.conf or whatever floats your boat)
> and drop it with a single command. It's not such a big deal as it is in
> Oracle.
>
> If this doesn't answer your question, could you say more about what your
> issue is?
>
> Regards,
> Paul
>
Thanks for your response,
that was exactly what I wanted to know. I was thinking about
pg_hba.conf but I was hoping there is some more elegant way
to do that :-)
Regards,
Lukas Houf
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Feigenbaum | 2008-05-05 18:03:09 | Re: bytea and character encoding when inserting escaped literals |
Previous Message | Tom Lane | 2008-05-05 17:36:01 | Re: operator varchar = integer |