Re: [GENERAL] close database, nomount state - Mailing list pgsql-general

From postgre@seznam.cz
Subject Re: [GENERAL] close database, nomount state
Date
Msg-id 1058.1480-28870-1538816510-1210009098@seznam.cz
Whole thread Raw
In response to Re: close database, nomount state  (paul rivers <privers@berkeley.edu>)
List pgsql-general
paul rivers <privers@berkeley.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

pgsql-general by date:

Previous
From: Lee Feigenbaum
Date:
Subject: Re: bytea and character encoding when inserting escaped literals
Next
From: Tino Wildenhain
Date:
Subject: Re: operator varchar = integer