On Thu, Aug 30, 2012 at 8:31 PM, Jeff Janes jeff.ja...@gmail.com wrote:
patch to do that attached.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
On Sat, Sep 1, 2012 at 12:00 AM, Peter Eisentraut pete...@gmx.net wrote:
When initializing a large database, pgbench writes tons of %d tuples
done lines. I propose to change this to a sort of progress counter
that stays on the same line, as in the attached patch.
I'm not sure I like this -
On 09/01/2012 12:28 PM, Robert Haas wrote:
Cross-link to doc build requirements from install requirements.
Jeff Janes
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e8d6c98c2f082bead1202b23e9d70e0fbde49129
Modified Files
--
On Mon, Aug 13, 2012 at 12:46:43PM +0200, Magnus Hagander wrote:
On Mon, Aug 13, 2012 at 4:34 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I've been experimenting with moving the Unix socket directory to
/var/run/postgresql for the Fedora distribution (don't ask :-().
It's mostly working, but I
On Sat, Sep 1, 2012 at 11:45:58AM -0400, Bruce Momjian wrote:
So, in summary, this patch moves the socket directory to the current
directory all but live check operation, and handles different socket
directories for old cluster = 9.1. I have added a documentation
mention of how to make this
Bruce Momjian br...@momjian.us writes:
On Sat, Sep 1, 2012 at 11:45:58AM -0400, Bruce Momjian wrote:
So, in summary, this patch moves the socket directory to the current
directory all but live check operation, and handles different socket
directories for old cluster = 9.1. I have added a
Bruce Momjian br...@momjian.us writes:
+ /*
+ * Report the Unix domain socket directory location to the
postmaster.
+ */
Report seems entirely the wrong verb there.
+ #define LISTEN_STR -c listen_addresses=''
+
+ /* Have a sockdir to use? */
+ if
On Sat, Sep 1, 2012 at 02:23:22PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
+ /*
+* Report the Unix domain socket directory location to the
postmaster.
+*/
Report seems entirely the wrong verb there.
+ #define LISTEN_STR -c
Bruce Momjian br...@momjian.us writes:
Well, you only want the unix_socket* if sockdir is defined, but you want
LISTEN_STR unconditionally, even if there is no sockdir.
Really? What will happen when the installation's default is to not
listen on any Unix socket? (unix_socket_directories = ''
On Sat, Sep 1, 2012 at 02:18:59PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
On Sat, Sep 1, 2012 at 11:45:58AM -0400, Bruce Momjian wrote:
So, in summary, this patch moves the socket directory to the current
directory all but live check operation, and handles different
On Sat, Sep 1, 2012 at 02:43:35PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Well, you only want the unix_socket* if sockdir is defined, but you want
LISTEN_STR unconditionally, even if there is no sockdir.
Really? What will happen when the installation's default is to
Bruce Momjian br...@momjian.us writes:
My point is that we are still going to need traditional connections for
live checks.
Yes, but that's not terribly relevant, IMO. All it means is that we
don't want to invent some solution that doesn't go through libpq.
If we could find a solution for
Bruce Momjian br...@momjian.us writes:
On Sat, Sep 1, 2012 at 02:43:35PM -0400, Tom Lane wrote:
I'm inclined to think that the no sockdir case is broken and you
should get rid of it. If you're starting a postmaster, you can and
should tell it a sockdir, period. If you're running a live
On Sat, Sep 1, 2012 at 03:06:57PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
On Sat, Sep 1, 2012 at 02:43:35PM -0400, Tom Lane wrote:
I'm inclined to think that the no sockdir case is broken and you
should get rid of it. If you're starting a postmaster, you can and
On Sat, Sep 1, 2012 at 03:05:01PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
My point is that we are still going to need traditional connections for
live checks.
Yes, but that's not terribly relevant, IMO. All it means is that we
don't want to invent some solution
On 1 Září 2012, 12:30, Robert Haas wrote:
On Sat, Sep 1, 2012 at 12:00 AM, Peter Eisentraut pete...@gmx.net wrote:
When initializing a large database, pgbench writes tons of %d tuples
done lines. I propose to change this to a sort of progress counter
that stays on the same line, as in the
[Properly posted to hackers list]
On Fri, Apr 1, 2011 at 02:27:02AM +1100, Brendan Jurd wrote:
On 1 April 2011 02:00, Adrian Klaver adrian.kla...@gmail.com wrote:
On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
If we wanted to make it work, then I think the thing to do would be
Robert Haas robertmh...@gmail.com writes:
On Tue, May 22, 2012 at 1:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Currently, the planner keeps paths that appear to win on the grounds of
either cheapest startup cost or cheapest total cost. It suddenly struck
me that in many simple cases (viz,
On Sat, Sep 1, 2012 at 06:23:59PM -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, May 22, 2012 at 1:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Currently, the planner keeps paths that appear to win on the grounds of
either cheapest startup cost or cheapest total
On Sat, Sep 1, 2012 at 11:45 AM, Bruce Momjian br...@momjian.us wrote:
On Mon, Aug 13, 2012 at 12:46:43PM +0200, Magnus Hagander wrote:
On Mon, Aug 13, 2012 at 4:34 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I've been experimenting with moving the Unix socket directory to
/var/run/postgresql for
-- Forwarded message --
From: Pavel Stehule pavel.steh...@gmail.com
Date: 2012/9/1
Subject: PATCH: psql boolean display
To: Phil Sorber p...@omniti.com
Hello
I am looking to your patch:
I have only one note. I don't think so using any text for values
true and false is good
Hi,
I'm experiencing the case when bitmap scan is ~ 70 times slower than
index scan which seems to be caused by 1) very big table 2) some hash
search logic (hash_search_with_hash_value )
Here is the explain analyze of the query with bitmap scans allowed:
wsdb= explain analyze select * from
22 matches
Mail list logo
