On Thu, November 29, 2012 17:16, Alvaro Herrera wrote:
Here it is.
fklocks-26.patch.gz
This applies today after removing, not only the infamous catversion.h chunk,
but also a file_fdw
chunk. (It's not really a problem.)
I also wondered if anyone has any perl/python/bash programs handy that
On 2012-12-22 10:53:47 +0100, Erik Rijkers wrote:
On Thu, November 29, 2012 17:16, Alvaro Herrera wrote:
Here it is.
fklocks-26.patch.gz
This applies today after removing, not only the infamous catversion.h chunk,
but also a file_fdw
chunk. (It's not really a problem.)
I also
Hi!
On Thu, Dec 6, 2012 at 5:44 AM, Tomas Vondra t...@fuzzy.cz wrote:
Then I've run a simple benchmarking script, and the results are not as
good as I expected, actually I'm getting much worse performance than
with the original GIN index.
The following table contains the time of loading the
Marko Kreen mark...@gmail.com writes:
On Fri, Dec 21, 2012 at 10:27 PM, Noah Misch n...@leadboat.com wrote:
How about instead calling RAND_cleanup() after each backend fork?
Not instead - the gettimeofday() makes sense in any case. Considering
that it's immediate problem only for pgcrypto,
Kohei KaiGai wrote:
RLS entry of wiki has not been updated for long time, I'll try to
update the entry for high-level design in a couple of days.
Thanks, I think that is essential for a productive discussion of
the issue.
For me, it would help tremendously if you could provide a very
short
I promised to research allowing parallel execution of schema
dump/restore, so I have developed the attached patch, with dramatic
results:
tables git patch
1000 22.2918.30
2000 30.7519.67
4000 46.3322.31
8000
On Sat, Dec 22, 2012 at 02:20:56PM -0500, Tom Lane wrote:
I believe that we'd be better off doing something in postmaster.c to
positively ensure that each session has a distinct seed value. Notice
that BackendRun() already takes measures to ensure that's the case for
the regular libc random()
Forgive me because I have been up for 28 hours on a 9.0 to 9.2 migration
with Hot Standby and PgPool-II for load balancing but I was excessively
irritated that I had to go into recovery.conf to configure things. I am
one of the software authors that breaking recovery.conf will cause
problems
On Sat, Dec 08, 2012 at 05:34:08PM +0100, Andres Freund wrote:
I made a pass through most of the commitfest entries to update their
state to something sensible and where it seemed necessary inquired the
newest status.
Not sure thats really welcome, but it was the only thing I could think
of
On 2012-12-22 14:20:56 -0500, Tom Lane wrote:
Marko Kreen mark...@gmail.com writes:
On Fri, Dec 21, 2012 at 10:27 PM, Noah Misch n...@leadboat.com wrote:
How about instead calling RAND_cleanup() after each backend fork?
Not instead - the gettimeofday() makes sense in any case. Considering
I'm testing a checkout from a few days ago and trying to complete a day
long pgbench stress test, with assertions and debugging on. I want to
make sure the base code works as expected before moving on to testing
checksums. It's crashing before finishing though. Here's a sample:
2012-12-20
11 matches
Mail list logo
