On Sun, 2012-06-24 at 01:26 +0300, Peter Eisentraut wrote:
About the new --maintenance-db options:
Why was this option not added to createuser and dropuser? In the
original discussion[0] they were mentioned, but it apparently never
made it into the code.
What should we do with this? Add
Peter Eisentraut pete...@gmx.net writes:
On Sun, 2012-06-24 at 01:26 +0300, Peter Eisentraut wrote:
About the new --maintenance-db options:
Why was this option not added to createuser and dropuser? In the
original discussion[0] they were mentioned, but it apparently never
made it into the
On Fri, Jun 29, 2012 at 3:32 PM, Bruce Momjian br...@momjian.us wrote:
On Mon, Jun 25, 2012 at 11:57:36AM -0400, Robert Haas wrote:
In retrospect, it seems as though it might have been a good idea to
make the postgres database read-only and undroppable, so that all
client utilities could count
On Sun, Jun 24, 2012 at 01:26:58AM +0300, Peter Eisentraut wrote:
About the new --maintenance-db options:
What is the purpose of these options? The initial discussion was
unclear on this. The documentation contains no explanation of why they
should be used. If we want to really support the
On Mon, Jun 25, 2012 at 11:57:36AM -0400, Robert Haas wrote:
In retrospect, it seems as though it might have been a good idea to
make the postgres database read-only and undroppable, so that all
client utilities could count on being able to connect to it and get a
list of databases in the
On Mon, Jun 25, 2012 at 02:58:25PM -0400, Robert Haas wrote:
On Mon, Jun 25, 2012 at 2:49 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400 2012:
Really, I think
pg_upgrade needs this option too, unless we're going to kill
On Mon, Jun 25, 2012 at 03:12:00PM -0400, Alvaro Herrera wrote:
Excerpts from Robert Haas's message of lun jun 25 14:58:25 -0400 2012:
On Mon, Jun 25, 2012 at 2:49 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400
Tom Lane t...@sss.pgh.pa.us writes:
Amit Kapila amit.kap...@huawei.com writes:
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
The implementation I've wanted to see for some time is that you can
start a standalone backend, but it speaks FE/BE protocol to its caller
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
Robert Haas robertmh...@gmail.com writes:
From pg_upgrade's perspective, it would
be nice to have a flag that starts the server in some mode where
nobody but pg_upgrade can connect to it
Amit Kapila amit.kap...@huawei.com writes:
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
The implementation I've wanted to see for some time is that you can
start a standalone backend, but it speaks FE/BE protocol to its caller
(preferably over pipes, so that there is no
On Sat, Jun 23, 2012 at 6:26 PM, Peter Eisentraut pete...@gmx.net wrote:
About the new --maintenance-db options:
Why was this option not added to createuser and dropuser? In the
original discussion[0] they were mentioned, but it apparently never made
it into the code.
Oops. That was an
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400 2012:
Really, I think
pg_upgrade needs this option too, unless we're going to kill the
problem at its root by providing a reliable way to enumerate database
names without first knowing the name one that you can connect to.
I
On Mon, Jun 25, 2012 at 2:49 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400 2012:
Really, I think
pg_upgrade needs this option too, unless we're going to kill the
problem at its root by providing a reliable way to enumerate
Excerpts from Robert Haas's message of lun jun 25 14:58:25 -0400 2012:
On Mon, Jun 25, 2012 at 2:49 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400 2012:
Really, I think
pg_upgrade needs this option too, unless we're
Robert Haas robertmh...@gmail.com writes:
From pg_upgrade's perspective, it would
be nice to have a flag that starts the server in some mode where
nobody but pg_upgrade can connect to it and all connections are
automatically allowed, but it's not exactly clear how to implement
nobody but
About the new --maintenance-db options:
Why was this option not added to createuser and dropuser? In the
original discussion[0] they were mentioned, but it apparently never made
it into the code.
I find the name to be unfortunate. For example, I think of running
vacuum as maintenance. So
On Saturday, June 23, 2012, Peter Eisentraut wrote:
About the new --maintenance-db options:
Why was this option not added to createuser and dropuser? In the
original discussion[0] they were mentioned, but it apparently never made
it into the code.
I find the name to be unfortunate. For
17 matches
Mail list logo
