Greg Smith g...@2ndquadrant.com writes:
On 06/14/2011 01:16 PM, Robert Haas wrote:
But there's no reason that code (which may or may not eventually prove
useful) has to be incorporated into the main tree. We don't commit
code so people can go benchmark it; we ask for the benchmarking to be
On 06/14/2011 07:08 PM, Tom Lane wrote:
I concur with Robert's desire to not push experimental code into the
main repository, but we need to have *some* way of working with it.
Maybe a separate repo where experimental branches could hang out would
be helpful?
Well, this one is sitting
On 06/14/2011 06:00 PM, Tom Lane wrote:
As far as Greg's proposal is concerned, I don't see how a proposed
addition of two columns would justify renaming an existing column.
Additions should not break any sanely-implemented application, but
renamings certainly will.
It's not so much
On 15/06/11 02:52, Cédric Villemain wrote:
2011/6/3 Mark Kirkwoodmark.kirkw...@catalyst.net.nz:
Corrected v4 patch with the test files, for completeness. Note that
discussion has moved on and there will be a v5 :-)
Mark, can you submit your updated patch ?
Thanks for the reminder! Here is
On Tue, Jun 14, 2011 at 4:41 PM, Jaime Casanova ja...@2ndquadrant.com wrote:
On Tue, Jun 14, 2011 at 4:14 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Alvaro Herrera's message of lun jun 13 18:08:12 -0400 2011:
Excerpts from Dean Rasheed's message of sáb jun 11 09:32:15
On Jun 14, 2011, at 3:45 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I've committed patches that fix these issues on my own OS X machine,
though it remains to be seen whether polecat and colugos will like
them. It turns out that whatever setup Robert has got with
'/Volumes/High Usage/' is really
Greg Smith wrote:
On 06/14/2011 06:00 PM, Tom Lane wrote:
As far as Greg's proposal is concerned, I don't see how a proposed
addition of two columns would justify renaming an existing column.
Additions should not break any sanely-implemented application, but
renamings certainly will.
On Tue, Jun 14, 2011 at 12:15 PM, Merlin Moncure mmonc...@gmail.com wrote:
I did a quick review and test of your patch. It didn't quite apply
cleanly due to recent non-related describe.c changes -- updated patch
attached.
Thanks for looking at this. Your updated patch looks good to me.
On Tue, Jun 14, 2011 at 3:25 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
pgindent moves strings back to the left when it thinks they fit within
80 columns. Yes, that seems pretty screwy.
I am losing track of the ways in which pgindent has managed to mangle
our source code :-/
Josh
On Wed, Jun 15, 2011 at 2:50 AM, Bruce Momjian br...@momjian.us wrote:
Agreed on moving 'IDLE' and 'IDLE in transaction' into separate
fields. If I had thought of it I would have done it that way years ago.
(At least I think it was me.) Using angle brackets to put magic values
in that field
On Wed, Jun 15, 2011 at 5:34 AM, Peter Eisentraut pete...@gmx.net wrote:
With gcc 4.6, I get this warning:
dblink.c: In function ‘dblink_send_query’:
dblink.c:620:7: warning: variable ‘freeconn’ set but not used
[-Wunused-but-set-variable]
I don't know much about the internals of dblink,
On 06/14/2011 06:09 PM, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
On 06/14/2011 05:45 PM, Tom Lane wrote:
I've committed patches that fix these issues on my own OS X machine,
Well, OSX is just using our usual *nix paraphernalia, so if it's broken
won't all such platforms
On Wed, Jun 15, 2011 at 11:41, Fujii Masao masao.fu...@gmail.com wrote:
ISTM that the root problem is that dblink_send_query calls DBLINK_GET_CONN
though it doesn't accept the connection string as an argument.
+1 for the fix. I have the same conclusion at the first glance.
Since the first
You might remember we added a postmaster/postgres -b switch to indicate
binary upgrade mode. The attached patch prevents any client without an
application_name of 'binary-upgrade' from connecting to the cluster
while it is binary upgrade mode. This helps prevent unauthorized users
from
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
For me, the litmus test is whether the change provides enough
improvement that it outweighs the disruption when the user runs into
it.
For the procpid that started all of this, the clear answer is no. I'm
surprised people seriously
Yesterday on PGXN I just released the first version of planinstr, a
plugin module to append planner time to EXPLAIN. I post this here
since it is mostly for developers.
http://www.pgxn.org/dist/planinstr/
db1=# load '$libdir/planinstr';
LOAD
db1=# explain select * from pg_class;
Bruce Momjian br...@momjian.us writes:
You might remember we added a postmaster/postgres -b switch to indicate
binary upgrade mode. The attached patch prevents any client without an
application_name of 'binary-upgrade' from connecting to the cluster
while it is binary upgrade mode. This
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
You might remember we added a postmaster/postgres -b switch to indicate
binary upgrade mode. The attached patch prevents any client without an
application_name of 'binary-upgrade' from connecting to the cluster
while it is binary
On Tue, Jun 14, 2011 at 6:17 PM, Greg Smith g...@2ndquadrant.com wrote:
Who said anything about this being a commit candidate? The WIP in the
subject says it's not intended to be. The community asks people to submit
design ideas early so that ideas around them can be explored publicly. One
On Tue, Jun 14, 2011 at 11:04 PM, Greg Sabino Mullane g...@turnstep.com wrote:
For me, the litmus test is whether the change provides enough
improvement that it outweighs the disruption when the user runs into
it.
For the procpid that started all of this, the clear answer is no. I'm
Previous version (at7-alt-index-opfamily.patch):
http://archives.postgresql.org/message-id/20110113230124.ga18...@tornado.gateway.2wire.net
Design:
http://archives.postgresql.org/message-id/20110524104029.gb18...@tornado.gateway.2wire.net
Patches committed in 2011CF1 allow ALTER TABLE ... ALTER
On 2011-06-15 05:01, Bruce Momjian wrote:
You might remember we added a postmaster/postgres -b switch to indicate
binary upgrade mode. The attached patch prevents any client without an
application_name of 'binary-upgrade' from connecting to the cluster
while it is binary upgrade mode. This
On Thu, Apr 21, 2011 at 12:18 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Apr 20, 2011 at 11:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I am a bit concerned about the reliability of this approach. If there
is some network lag, or some lag in
101 - 123 of 123 matches
Mail list logo
