On postgresql anniversary summit there was a presentation byt SRA people
about using background writer to do CHECKPOINTs which seemed very
effective for removing the performance gap caused by CHECKPOINT.
Has any of it been submitted for 8.2 ?
--
Hannu Krosing
Database Architect
Hannu Krosing wrote:
On postgresql anniversary summit there was a presentation byt SRA people
about using background writer to do CHECKPOINTs which seemed very
effective for removing the performance gap caused by CHECKPOINT.
Has any of it been submitted for 8.2 ?
No, I don't remember seeing
On Thu, Aug 17, 2006 at 08:20:22PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Have you tried to use debbugs? I agree with Greg Stark that it's a
better fit for our current procedure, while enabling better
traceability.
The principal strike against debbugs seems to
On Thu, 2006-08-17 at 19:11 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Revised patch enclosed, now believed to be production ready. This
implements regular log switching using the archive_timeout GUC.
Further patch enclosed implementing these changes plus the record type
I noticed a minor annoyance while testing: when the system is
completely idle, you get a forced segment switch every
checkpoint_timeout seconds, even though there is nothing
useful to log. The checkpoint code is smart enough not to do
a checkpoint if nothing has happened since the last
Hello,
I had a customer call in today they are running Win2003 with 22 gig
of ram (that may be a mistype on their end, it may be 32gigs of
ram).
They cranked up their postgresql max_connections to 500.
When PostgreSQL hits above 400, it dies and I don't mean a slow
crawl type death. A
Hi guys,
I've attached as much as I've done so far on the GIN docs. It's not a
lot, but I'm afraid with the feature freeze in effect, I'm just not
going to have the ability to get them done by the RC date.
The main problem was I just strugged to fully understand it all :(
Anyway, hopefully
Maybe this article can help:
Windows and the ClearCase process limit: Understanding the
desktop
heap
http://www-
128.ibm.com/developerworks/rational/library/05/1220_marecha
l/
i doubled all my heap settings and was able to roughly double the -
c
on pgbench from ~158 (stock) to
Hannu Krosing [EMAIL PROTECTED] wrote:
On postgresql anniversary summit there was a presentation byt SRA people
about using background writer to do CHECKPOINTs which seemed very
effective for removing the performance gap caused by CHECKPOINT.
Has any of it been submitted for 8.2 ?
That's
Hi James,
I just wanted to inform you all that I solve the issue, it was
indeed the nul device as James and Martijn mention.
I have change the source to redirect the output to a log file, to
which I gave permission to the postgres user.
The file (currently) is created at the temp
Since I have a stuck backend without client again, I'll have to
kill
-SIGTERM a backend. Fortunately, I do have console access to
that
machine and it's not win32 but a decent OS.
You do know that on Windows you can use pg_ctl to send a pseudo
SIGTERM to a backend, don't you?
The
Magnus Hagander wrote:
Since I have a stuck backend without client again, I'll have to
kill
-SIGTERM a backend. Fortunately, I do have console access to
that
machine and it's not win32 but a decent OS.
You do know that on Windows you can use pg_ctl
SIGFPE is a synchornous signal and Windows will raise it if proper
flag is set (check out the example program):
http://msdn2.microsoft.com/en-us/library/kfy34skx.aspx
But seems we didn't use the above method. Instead, we use the same
methodology as other asynchrounous signals. My
Hi,
I just finished setting up a new buildfarm member (Bandicoot)
running Windows 2000 Pro. Aside from the fact that it now fails
with the same cyptic pg_regress error as seen on Snake, it also
became apparent that CVS HEAD won't run properly on an unpatched
Windows 2000 (initdb - and
Per discussion at the conference:
In order to run the regression tests on Windows without msys,
pg_regress needs to be reimplemnted in C.
This has some minor portability issues (macros with ... aren't
portable, for instance) but I think it's something we need to do.
Barring objections
Am Donnerstag, 17. August 2006 18:40 schrieb Josh Berkus:
I'm in favor of this, but do we want to turn on vacuum_delay by default
as well?
People might complain that suddenly their vacuum runs take four times as long
(or whatever). Of course, if we turn on autovacuum and advocate a more or
Have you been able to determine *why* Microsoft made this
braindead
decision? Or where it's documented? Their own knowledgebase is
filled
with examples of using the device, so I imagine they'll have to
post a
workaround somewhere...
AFAIK, nobody has posted any links to information
Am Donnerstag, 17. August 2006 20:05 schrieb Chris Mair:
\gc sounds like a good idea to me :)
Strictly speaking, in the randomly defined grammer of psql, \gc is \g with an
argument of 'c' (try it, it works).
I'm not sure what use case you envision for this feature. Obviously, this is
for
Am Donnerstag, 17. August 2006 17:17 schrieb stark:
Instead I just added a command to cause psql to wait for a time.
Do we need the full multiple-connection handling command set, or would
asynchronous query support and a wait command be enough?
--
Peter Eisentraut
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2006-08-17 at 19:11 -0400, Tom Lane wrote:
I noticed a minor annoyance while testing: when the system is completely
idle, you get a forced segment switch every checkpoint_timeout seconds,
even though there is nothing useful to log. The checkpoint
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
Just guessing from the function name, but does this go away if you
don't configure --with-ldap?
If so it's presumably a portability issue in this recent patch:
2006-03-06 12:41 momjian
* configure, configure.in, src/backend/libpq/auth.c,
src/backend/libpq/hba.c,
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Have you tried to use debbugs? I agree with Greg Stark that it's a
better fit for our current procedure, while enabling better
traceability.
The principal strike against debbugs seems to be that the source code is
not readily
Magnus Hagander [EMAIL PROTECTED] writes:
Though for the Windows case only, we could easily enough make it
possible to run pg_ctl kill remotely, since we use a named pipe. Does
this seem like a good or bad idea?
Seems like we'd be opening a can of security worms :-(
Peter Eisentraut wrote:
Am Donnerstag, 17. August 2006 18:40 schrieb Josh Berkus:
I'm in favor of this, but do we want to turn on vacuum_delay by default
as well?
People might complain that suddenly their vacuum runs take four times as long
(or whatever). Of course, if we turn on autovacuum
Though for the Windows case only, we could easily enough make it
possible to run pg_ctl kill remotely, since we use a named pipe.
Does
this seem like a good or bad idea?
Seems like we'd be opening a can of security worms :-(
Not really, standard windows ACL already applies to
Andrew Dunstan wrote:
I see that the installcheck-parallel was not added to the top level
Makefile and Gnumakefile.in when it was added as a regression test
target back in the 8.0 cycle. Is there any objection to my adding it
now so that it is treated the same as the other regression test
On Fri, Aug 18, 2006 at 02:46:39PM +0200, Peter Eisentraut wrote:
Am Donnerstag, 17. August 2006 17:17 schrieb stark:
Instead I just added a command to cause psql to wait for a time.
Do we need the full multiple-connection handling command set, or would
asynchronous query support and a
stark wrote:
Alvaro Herrera alvherre ( at ) commandprompt ( dot ) com writes:
Maybe we could write a suitable test case using Martijn's concurrent
testing framework.
The trick is to get process A to commit between the times that process B
looks at the new and old versions of the
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
Tom Lane wrote:
Vacuum's always had a race condition: it makes a list of rel OIDs and
then tries to vacuum each one. It narrows the window for failure by
doing a SearchSysCacheExists test before relation_open, but there's
still a window for
Peter Eisentraut [EMAIL PROTECTED] writes:
Does anyone, for that matter, want to propose possible default parameters for
vacuum_delay?
I haven't seen any sign that anyone's done any serious testing of delay
parameters, so I don't think we have the data needed to select some
defaults ...
Peter Eisentraut [EMAIL PROTECTED] writes:
A \set variable would make sense to me.
So Peter and Bruce like a \set variable, Chris and I like a different
command. Seems like a tie ... more votes out there anywhere?
regards, tom lane
---(end of
On Aug 17 10:38, Tom Lane wrote:
Volkan YAZICI [EMAIL PROTECTED] writes:
I've still biten by a single write past chunk error while returning a
record in PL/scheme:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x84a0598, chunk 0x84a0c84
The
The procedure entry point ldap_start_tls_sA could not be located in
the
dynamic link library wldap32.dll.
I'd counsel just leaving --with-ldap off until Magnus gets back
from vacation. We can always revert the patch later if he can't
fix it.
Looking at the MSDN documentation it seems
Volkan YAZICI [EMAIL PROTECTED] writes:
Looks like my palloc() math was correct. Just I had missed special
handling of attnulls array passed to heap_formtuple(). It had should be
attnulls[i] = (isnull) ? 'n' : ' ';
These days I'd use heap_form_tuple in new code --- then you can work
with
Andrew Dunstan wrote:
Andrew Dunstan wrote:
I see that the installcheck-parallel was not added to the top level
Makefile and Gnumakefile.in when it was added as a regression test
target back in the 8.0 cycle. Is there any objection to my adding it
now so that it is treated the same
Hi all..
There's some way to find the template of a database in SQL (using 7.4)?
[]'s
- Walter
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
Magnus Hagander wrote:
Hi,
I just finished setting up a new buildfarm member (Bandicoot)
running Windows 2000 Pro. Aside from the fact that it now fails
with the same cyptic pg_regress error as seen on Snake, it also
became apparent that CVS HEAD won't run properly on an unpatched
Bruce Momjian wrote:
I have updated the 8.0 release notes to say Windows 2000SP4 supported.
Not to nitpick, but I think you should change supported to *required*.
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 4: Have you
Joshua D. Drake wrote:
Bruce Momjian wrote:
I have updated the 8.0 release notes to say Windows 2000SP4 supported.
Not to nitpick, but I think you should change supported to *required*.
I am worried that saying required means it only works for that version,
while it might work for
I am worried that saying required means it only works for that version,
while it might work for SP5 if that is ever released.
How about:
Windows 2000 SP4 and above required.
I know it seems trivial, but the amount of people that run windows I
really don't want to spend
a ton of time
Walter Cruz wrote:
Hi all..
There's some way to find the template of a database in SQL (using 7.4)?
Find the template? Could you clarify your question?
[]'s
- Walter
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
well, when I create a database, it inherits from template1
When I have a table that I don't know if it inherits from template 1,
how can I find the 'super' ?
[]'s
- Walter
On 8/18/06, Joshua D. Drake [EMAIL PROTECTED] wrote:
Walter Cruz wrote:
Hi all..
There's some way to find the template
Walter Cruz wrote:
well, when I create a database, it inherits from template1
When I have a table that I don't know if it inherits from template 1,
how can I find the 'super' ?
I do not believe that tables have templates in 7.4 unless you specifically
use a query like:
create table foo as
Walter Cruz [EMAIL PROTECTED] writes:
well, when I create a database, it inherits from template1
When I have a table that I don't know if it inherits from template 1,
how can I find the 'super' ?
There isn't any persistent inheritance relationship for databases.
CREATE DATABASE just copies the
When I have a table that I don't know if it inherits from template 1,
how can I find the 'super' ?
I do not believe that tables have templates in 7.4 unless you specifically
use a query like:
create table foo as select * from bar;
I think Walter wants to know if a given table was
This is my first post to a PostgreSQL mailing list, so please forgive me
if I have posted to the wrong place
Currently pg_dump has flags for dumping only table definitions and/or
data. These flags are respectively:
--schema-only
--data-only
I propose that two more be added:
--tables-only
Naz Gassiep [EMAIL PROTECTED] writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many objects in a
database that are definitely neither tables nor constraints, and it's
not very clear what things should be considered
Tom Lane wrote:
Naz Gassiep [EMAIL PROTECTED] writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many objects in a
database that are definitely neither tables nor constraints, and it's
not very
I am worried that saying required means it only works for that
version, while it might work for SP5 if that is ever released.
How about:
Windows 2000 SP4 and above required.
Yeah, that's better wording. Or more correct I think Windows 2000 SP4
or above.
FWIW, MS has officially said
On Fri, Aug 18, 2006 at 10:16:12AM -0400, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
A \set variable would make sense to me.
So Peter and Bruce like a \set variable, Chris and I like a
different command. Seems like a tie ... more votes out there
anywhere?
It seems to me
On Friday 18 August 2006 18:52, Tom Lane wrote:
Naz Gassiep [EMAIL PROTECTED] writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many objects in a
database that are definitely neither tables nor constraints, and
Andreas Joseph Krogh wrote:
On Friday 18 August 2006 18:52, Tom Lane wrote:
Naz Gassiep [EMAIL PROTECTED] writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many objects in a
I think what you may really be after is the stuff that should be loaded
before inserting data and the stuff that should be loaded after, but
the above are poor names for these concepts.
But it certainly would be nice to be able to dump all that stuff:-)
Yea, I've been told that this
Joshua D. Drake wrote:
I think what you may really be after is the stuff that should be
loaded
before inserting data and the stuff that should be loaded after,
but
the above are poor names for these concepts.
But it certainly would be nice to be able to dump all that stuff:-)
Yea,
-Original Message-
From: Magnus Hagander [mailto:[EMAIL PROTECTED]
Sent: Fri 8/18/2006 12:46 PM
To: Dave Page; pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] Windows 2000 Support
(btw, clinically insane without patching it.. And obviously you didn't
patch yours? :-P)
Yeah,
Andrew Dunstan wrote:
We already have a highly selective and configurable restore mechanism,
using the -L feature of pg_restore. Maybe there's a good special case
for this particular split, but it is hardly undoable now.
As for Naz' needs - I gave him a perl script I whipped up in few
Andrew Dunstan wrote:
Joshua D. Drake wrote:
I think what you may really be after is the stuff that should be
loaded
before inserting data and the stuff that should be loaded after,
but
the above are poor names for these concepts.
But it certainly would be nice to be able to
Volkan YAZICI [EMAIL PROTECTED] writes:
I've prepared a new patch that adds below commands to the libpq:
/* Accessor functions for PGresParamDesc field of PGresult. */
int PQnparams(const PGresult *res)
int PQparamType(const PGresult *res, int param_num)
/* Async functions. */
Alvaro Herrera wrote:
Andrew Dunstan wrote:
Joshua D. Drake wrote:
I think what you may really be after is the stuff that should be
loaded
before inserting data and the stuff that should be loaded after,
but
the above are poor names for these concepts.
But it
Andrew Dunstan [EMAIL PROTECTED] writes:
Well, the other issue is how many canned breakup schemes we are going to
support. If this particular one is of sufficiently general usefulness
then I have no objection. But when you can produce it trivially from the
output of pg_dump -s, the need to
Anyone in a position to review the pending plpython patch?
http://archives.postgresql.org/pgsql-patches/2006-08/msg00151.php
After that little fiasco with plperl I'm disinclined to apply anything
without review by somebody who's pretty familiar with the PL in
question ... and Python's not my
All,
I chatted some with some of the Debian folks who maintain Debbugs. They
thought it would take a significant amount of work to adapt it to
PostgreSQL, in addition to the obvious needs to improve the web interface.
RT has some significant short comings for our project such as not having
On Fri, Aug 18, 2006 at 04:27:23PM -0400, Tom Lane wrote:
Anyone in a position to review the pending plpython patch?
http://archives.postgresql.org/pgsql-patches/2006-08/msg00151.php
In several places the code does this:
so = PyObject_Str(value);
valuestr = PyString_AsString(so);
Tom Lane wrote:
Anyone in a position to review the pending plpython patch?
http://archives.postgresql.org/pgsql-patches/2006-08/msg00151.php
After that little fiasco with plperl I'm disinclined to apply anything
without review by somebody who's pretty familiar with the PL in
question ... and
Magnus Hagander wrote:
Yeah, that's better wording. Or more correct I think Windows 2000
SP4 or above.
FWIW, MS has officially said at some point that they will not make
SP5 for Windows 2000, but they've changed their minds before...
Unless there actually is a version of that operating
Greg Sabino Mullane [EMAIL PROTECTED] writes:
More to come, but these two are probably worth backpatching.
We can't really backpatch changes to information_schema, since we can't
force initdb in back branches.
I'd be interested to see you cite chapter and verse in the SQL spec
where it says
So, the question is whether any of our biggest bug-fixers would dig in
their heels and scream No! if we gave BugZilla a try. Comments?
I could have this setup this weekend should we vote YES :)
Joshua D. Drake
---(end of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd be interested to see you cite chapter and verse in the SQL spec
where it says that information_schema should hide temp tables of
other backends. That change seems pretty dubious to me. (More
likely, we should be adding tests on whether the
David Fetter wrote:
On Fri, Aug 18, 2006 at 10:16:12AM -0400, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
A \set variable would make sense to me.
So Peter and Bruce like a \set variable, Chris and I like a
different command. Seems like a tie ... more votes out there
Peter Eisentraut wrote:
Magnus Hagander wrote:
Yeah, that's better wording. Or more correct I think Windows 2000
SP4 or above.
FWIW, MS has officially said at some point that they will not make
SP5 for Windows 2000, but they've changed their minds before...
Unless there actually is a
71 matches
Mail list logo
