Prev: Should database = all in pg_hba.conf match a replication connection?
Next: recovery_connections cannot start (was Re: [HACKERS] master instandby mode croaks)
From: Simon Riggs on 21 Apr 2010 12:32
On Wed, 2010-04-21 at 11:53 -0400, Tom Lane wrote:
> Simon Riggs <simon(a)2ndQuadrant.com> writes:
> > On Wed, 2010-04-21 at 14:37 +0300, Heikki Linnakangas wrote:
> >> I also think we shouldn't be fiddling with this at this stage in the
> >> release cycle.
>
> > OK, but not because I see a problem with the technique.
>
> You made that plain already, but you have not convinced anyone else.

Not pouting, just recording the fact that its an ongoing discussion.

> More to the point, ALTER SET TABLESPACE is not an operation that
> happens so much that we ought to take any risks to optimize it.

I think its the opposite: people don't run it because they can't.

But I'm happy not to press further at this stage of 9.0. I am always
optimistic about convincing you ;-)

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  | 
Pages: 1 2
Prev: Should database = all in pg_hba.conf match a replication connection?
Next: recovery_connections cannot start (was Re: [HACKERS] master instandby mode croaks)