On Sat, 2006-07-15 at 21:10 -0400, Greg Stark wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Another related thing - throttling
--
Did you do any work on using vacuum_cost_* GUC vars to throttle the
build process if desired ?
Actually no. While
Ühel kenal päeval, L, 2006-07-15 kell 22:24, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
And by any chance, do you plan to backport the standby WAL playback mode
patches to 8.0 and 8.1 series ?
That's not happening ... we do not put new features in stable branches.
Not even
Ühel kenal päeval, L, 2006-07-15 kell 21:10, kirjutas Greg Stark:
Hannu Krosing [EMAIL PROTECTED] writes:
Maybe we can show progress indicators in status line (either
pg_stat_activity.current_query or commandline shown in ps), like
WAITING TO START PHASE 1 - WAITING FOR TRANSACTION
What's wrong with this picture?
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
Notice how all the red is at the bottom of the report? That's because
all the Windows machines are at the bottom, indicating that they haven't
reported recently. AFAICT, snake is the only Windows machine that
On Sun, 16 Jul 2006, Tom Lane wrote:
[windows buildfarm machines run irregularly]
For my part the difficulty is scheduling. As a primarily unix user I
understand cron, but have no idea what the windows equivalent is. For my
cygwin buildfarm member I setup cron, but the make step failed
Andreas Seltenreich [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
[2. text/x-patch; restartableRecovery.patch]
Hmm, wouldn't you have to reboot the resource managers at each
checkpoint? I'm afraid otherwise things like postponed page splits
could get lost on restart from a
On Saturday 15 July 2006 21:37, Joshua D. Drake wrote:
That said I'm not sure how much I can do here. For a substantial index we
should expect most of the time will be spent in the tuplesort. It's hard
to see how to get any sort of progress indicator out of there and as long
as we can't
On Sun, 2006-07-16 at 10:51 -0400, Tom Lane wrote:
Andreas Seltenreich [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
[2. text/x-patch; restartableRecovery.patch]
Hmm, wouldn't you have to reboot the resource managers at each
checkpoint? I'm afraid otherwise things like
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tom Lane
Sent: Sun 7/16/2006 3:29 PM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] Windows buildfarm support, or lack of it
AFAICT, snake is the only Windows machine that
actually runs the buildfarm on a regular schedule,
-Original Message-
From: Kris Jurka [mailto:[EMAIL PROTECTED]
Sent: Sun 7/16/2006 3:44 PM
To: Tom Lane
Cc: pgsql-hackers@postgreSQL.org; Dave Page
Subject: Re: [HACKERS] Windows buildfarm support, or lack of it
For my part the difficulty is scheduling. As a primarily unix user I
The latest buildfarm report from trout,
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=troutdt=2006-07-16%2014:36:19
shows a failure mode that we've seen recently on snake, but not for a
long time on any non-Windows machines: the stats test fails with
symptoms suggesting that the stats counters
Kris Jurka wrote:
On Sun, 16 Jul 2006, Tom Lane wrote:
[windows buildfarm machines run irregularly]
For my part the difficulty is scheduling. As a primarily unix user I
understand cron, but have no idea what the windows equivalent is. For
my cygwin buildfarm member I setup cron, but
Simon Riggs [EMAIL PROTECTED] writes:
On Sun, 2006-07-16 at 10:51 -0400, Tom Lane wrote:
Ouch. That's a bit nasty. You can't just apply a postponed split at
checkpoint time, because the WAL record could easily be somewhere after
the checkpoint, leading to duplicate insertions.
To do this
Dave Page wrote:
I have spare licences for most versions of Windows as well, so if Microsoft's
virtual server product is not too expensive for us I can probably add a few
platform variations to that box. I'll look into it.
In fact MS released Virtual PC 2004 for free a couple days ago
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tom Lane
Sent: Sun 7/16/2006 3:29 PM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] Windows buildfarm support, or lack of it
AFAICT, snake is the only Windows machine that
actually runs the buildfarm on
Andrew Dunstan [EMAIL PROTECTED] writes:
Dave Page wrote:
I can bump that up as high as you'd like within reason. 4? 6 times a day?
Let's go for 6, at least for HEAD.
There's probably no need to check the back branches oftener than once a
day, but if you can do HEAD every 4 hours that'd be
-Original Message-
From: Petr Jelinek [EMAIL PROTECTED]
To: Dave Page dpage@vale-housing.co.uk
Cc: PostgreSQL-development pgsql-hackers@postgresql.org
Sent: 16/07/06 18:05
Subject: Re: Windows buildfarm support, or lack of it
In fact MS released Virtual PC 2004 for free a couple days
Andrew, Tom:
I'm putting a solicitation in this week's PWN for more Windows buildfarm
members. With 250,000 Windows+PostgreSQL users out there, you'd think a few
people would step up.
Dave, I think you may need to give Andrew Windows buildfarm instructions to
put up at www.pgbuildfarm.org.
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Dave Page wrote:
I can bump that up as high as you'd like within reason. 4? 6 times a day?
Let's go for 6, at least for HEAD.
There's probably no need to check the back branches oftener than once a
day, but if you can do HEAD every
Folks,
Hopefully by now a bunch of you have joined as Software in the Public Interest
Contributing members per my earlier e-mail and are aware that the SPI annual
board election has started. If you are a registered contributing member
with SPI, elections are at:
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 16 July 2006 18:47
To: Andrew Dunstan
Cc: Dave Page; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Windows buildfarm support, or lack of it
Andrew Dunstan [EMAIL PROTECTED] writes:
Dave Page wrote:
I
-Original Message-
From: Stefan Kaltenbrunner [mailto:[EMAIL PROTECTED]
Sent: 16 July 2006 18:17
To: Dave Page
Subject: Re: [HACKERS] Windows buildfarm support, or lack of it
care to share that script ? I set up seahorse on friday but as a
unix-sysadmin I have not yet managed
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: 16 July 2006 19:04
To: pgsql-hackers@postgresql.org
Cc: Tom Lane; Andrew Dunstan; Dave Page
Subject: Re: [HACKERS] Windows buildfarm support, or lack of it
Andrew, Tom:
I'm putting a solicitation in this
I wrote:
But ... AFAICS the only signal that could plausibly be arriving at the
stats collector is SIGALRM from its own use of setitimer() to schedule
stats file writes. So it seems that this failure occurs when the alarm
fires between the select() and recv() calls; which is possible but it
On Sun, 2006-07-16 at 12:40 -0400, Tom Lane wrote:
A compromise that might be good enough is to add an rmgr routine defined
as bool is_idle(void) that tests whether the rmgr has any open state
to worry about. Then, recovery checkpoints are done only if all rmgrs
say they are idle.
Like
Dave Page dpage@vale-housing.co.uk writes:
In fact MS released Virtual PC 2004 for free a couple days ago
(http://www.microsoft.com/windows/virtualpc/default.mspx)
Yeah - I have licences for it, but it's more of an interactive emulator. I
think I'll need the server version to run fully
Simon Riggs [EMAIL PROTECTED] writes:
On Sun, 2006-07-16 at 12:40 -0400, Tom Lane wrote:
A compromise that might be good enough is to add an rmgr routine defined
as bool is_idle(void) that tests whether the rmgr has any open state
to worry about. Then, recovery checkpoints are done only if
On Sun, 2006-07-16 at 15:33 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Sun, 2006-07-16 at 12:40 -0400, Tom Lane wrote:
A compromise that might be good enough is to add an rmgr routine defined
as bool is_idle(void) that tests whether the rmgr has any open state
to
Kris Jurka wrote:
For my cygwin buildfarm member I setup cron, but the make step
failed for every build for unknown reasons while succeeding if not run
from cron.
Is this still happening? We should try to get to the bottom of it.
cheers
andrew
---(end of
-Original Message-
From: Andrew Dunstan [EMAIL PROTECTED]
To: Peter Eisentraut [EMAIL PROTECTED]
Cc: pgsql-hackers@postgresql.org pgsql-hackers@postgresql.org
Sent: 16/07/06 23:50
Subject: Re: [HACKERS] automatic system info tool?
We also classify buildfarm machines by os, os_version,
Hello,
We were going to submit plPHP to core for inclusion but it is not ready
yet. Namely it requires the apache SAPI which could introduce some
portability issues. The other issues it has (such as some array parsing
problems) are minor and could probably be fixed easily within the beta
On Sun, 16 Jul 2006, Joshua D. Drake wrote:
Hello,
However plRuby is even a stranger beast as it uses an entirely ruby
build system. I am also fairly confident that it does not meat the
PostgreSQL style guidelines.
Well... JDBC used its own.
Is there enough interest in plRuby to get it
On 7/16/06, Joshua D. Drake [EMAIL PROTECTED] wrote:
Kris Jurka wrote: On Sun, 16 Jul 2006, Tom Lane wrote: [windows buildfarm machines run irregularly] For my part the difficulty is scheduling.As a primarily unix user I
understand cron, but have no idea what the windows equivalent is.For my
Sorry- perhaps I misunderstand the purpose of your group, but how can
you claim to be making decisions on software in the public interest
on a private, paid-member mailing list?
-M
On Jul 16, 2006, at 2:10 PM, Josh Berkus wrote:
Folks,
Hopefully by now a bunch of you have joined as
Agent M wrote:
Sorry- perhaps I misunderstand the purpose of your group, but how can
you claim to be making decisions on software in the public interest on
a private, paid-member mailing list?
Well it isn't paid-member mailing (I don't think) but you do need to be
a contributing member (ahh
Hi,
when searching the TODO list (http://www.postgresql.org/docs/faqs.TODO.html).
i found this on the Monitoring section:
o Allow protocol-level BIND parameter values to be logged
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php
But i don't understand why that thread is
Sorry, i'm resending because i forgot the subject
On 7/17/06, Jaime Casanova [EMAIL PROTECTED] wrote:
Hi,
when searching the TODO list (http://www.postgresql.org/docs/faqs.TODO.html).
i found this on the Monitoring section:
o Allow protocol-level BIND parameter values to be logged
On Mon, Jul 17, 2006 at 12:25:09AM -0500, Jaime Casanova wrote:
when searching the TODO list
(http://www.postgresql.org/docs/faqs.TODO.html).
i found this on the Monitoring section:
o Allow protocol-level BIND parameter values to be logged
38 matches
Mail list logo
