see:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=haredt=2004-12-10%2005:15:05
cheers
andrew
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL
I had to fix an old, badly written web application, it had some performance
problems sometimes. I found out there are some links broken:
http://./?id=123456778995934853
in fact the link should be:
http://./?id=123456778995934853
where the part 78995934853 was random and should force a
Sibtay Abbas [EMAIL PROTECTED] writes:
for the handler function i ve followed the following
template
PG_FUNCTION_INFO_V1(myhandler);
^
Datum
plsample_call_handler(PG_FUNCTION_ARGS)
^
Try spelling the function name consistently.
The idea that bgwriter smooths out the response time of transactions is
only true if the buffer lists T1 and T2 have *some* clean buffers
available for use when performing I/O. The alternative is that
transactions unlucky enough to encounter the no-clean-buffers situation
have to clean a space for
On Thu, 2004-12-09 at 21:21, Mark Wong wrote:
On Mon, Dec 06, 2004 at 07:52:37PM +, Simon Riggs wrote:
Varying bgwriter_maxpages upwards should take performance higher.
I have 2 runs now. I for both tests, I have bgwriter_percent=100,
checkpoint_segments=8192, checkpoint_timout=600,
Alvaro Herrera [EMAIL PROTECTED] writes:
I have been working on the patch and it seems now it works as I
originally intended it to: dropping users or tablespaces is disallowed
unless they own or contain no object. ACL's are not tracked; I'm still
unsure if they should be.
If we fail to track
I'm a beginning developer to postgresql working on a CS Master's project trying
to implement a new join operator. My question is how to effectively break down
a TupleTableSlot into it's properties. I've been messing around with it for
hours now and thought the code below would return the
Hello,
==
All 96 tests passed.
==
$ uname -a
Linux pergolesi 2.4.26 #1 SMP Mon May 24 11:59:02 CEST 2004 x86_64 GNU/Linux
postgresql-8.0.0rc1 build on Debian GNU/Linux sid.
Sadly tcl and pam devel files weren't installed so I could just use (I'm
not
Hello,
==
All 96 tests passed.
==
$ uname -a
Linux crest 2.4.26-amiga #1 Thu Apr 22 00:21:18 CEST 2004 m68k GNU/Linux
postgresql-8.0.0rc1 build on Debian GNU/Linux sid.
--
Nol Kthe noel debian.org
Debian GNU/Linux, www.debian.org
signature.asc
Hello,
==
All 96 tests passed.
==
$ uname -a
Linux vore 2.4.26 #1 SMP Tue Apr 20 14:16:21 EDT 2004 sparc64 GNU/Linux
postgresql-8.0.0rc1 build on Debian GNU/Linux sid.
--
Nol Kthe noel debian.org
Debian GNU/Linux, www.debian.org
signature.asc
Port report for Solaris 8: No errors.
uname -a:
SunOS sunos58.build 5.8 Generic_117350-11 sun4u sparc SUNW,UltraAX-i2
gcc -v:
Reading specs from
/gcc-3.4.0/sunos5/bin/../lib/gcc/sparc-sun-solaris2.8/3.4.0/specs
Configured with: /gcc-3.4.0/src/dist/configure --prefix=/usr/site/gcc-3.4.0
[EMAIL PROTECTED] (Bruce Momjian) writes:
Kenneth Marshall wrote:
Let me ask --- if you change the CC line in Makefile.global to cc_r,
does everything build OK? That might be a clean solution because the
change could be made in one place. Of course this would mean the
backend would also
Schoudel, Brian [EMAIL PROTECTED] writes:
I'm a beginning developer to postgresql working on a CS Master's project
trying to implement a new join operator. My question is how to effectively
break down a TupleTableSlot into it's properties. I've been messing around
with it for hours now
Andrew Dunstan [EMAIL PROTECTED] writes:
Further investigation has shown that the exit/trap idiom used in
pg_regress.sh is less than 100% portable.
The following shell script has been seen to produce incorrect output on
both Cygwin and FreeBSD:
This is distinctly less than credible. If it
Hello
$ uname -a
Darwin Computer.local 7.5.0 Darwin Kernel Version 7.5.0: Thu Aug 5
19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC Power
Macintosh powerpc
./configure --with-includes=/sw/include --with-libs=/sw/lib
--enable-thread-safety --with-perl --with-python --with-krb5
Andrew Dunstan wrote:
Further investigation has shown that the exit/trap idiom used in
pg_regress.sh is less than 100% portable.
The following shell script has been seen to produce incorrect output
on both Cygwin and FreeBSD:
#!/bin/sh
trap '
st=$?
echo status = $st
exit $st
'
Darcy Buskermolen wrote:
It looks like --enable-cassert isn't handled properly under icc7
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=herringdt=2004-12-
07%2016:30:44
That is quite a superficial display of the issue. If you want to get to
the bottom of this, you need to, uh, dig
Peter Eisentraut wrote:
Andrew Dunstan wrote:
Further investigation has shown that the exit/trap idiom used in
pg_regress.sh is less than 100% portable.
The following shell script has been seen to produce incorrect output
on both Cygwin and FreeBSD:
#!/bin/sh
trap '
st=$?
echo status = $st
Alvaro Herrera wrote:
I had thought that maybe we shouldn't track dependencies on the first
superuser, on the assumption that it cannot be dropped. I'm not sure
if this is entirely true however.
Well, there are certainly nontrivial provisions for recovering
installations where it has been
Some time ago, Grant Finnemore [EMAIL PROTECTED] wrote:
TRAP: FailedAssertion(!(((ntp)-t_data)-t_infomask 0x0010), File:
catcache.c, Line: 1728)
I think we finally figured out where this came from:
http://archives.postgresql.org/pgsql-bugs/2004-12/msg00128.php
Mark Wong [EMAIL PROTECTED] writes:
I never vacuum during the test. Is it possible that all the updates
and inserts would affect this?
That's bad; first because it possibly *is* hurting performance, and
second because if it isn't, your results could legitimately be attacked
as not representing
I wonder if we even need to retain the bgwriter_percent GUC var. Is
there actually a situation in which the combination of bgwriter_maxpages
and bgwriter_delay does not give the DBA sufficient flexibility in
tuning bgwriter behavior?
Simon Riggs wrote:
If the bgwriter_percent = 100, then we
Ed L. [EMAIL PROTECTED] writes:
CREATE TABLE foo ( key serial NOT NULL PRIMARY KEY, msg character(100));
CREATE TABLE bar ( key serial NOT NULL PRIMARY KEY, msg character(100));
CREATE VIEW baz AS SELECT * FROM foo UNION ALL SELECT * FROM bar;
CREATE OR REPLACE VIEW baz AS SELECT * FROM foo;
On Mon, Dec 06, 2004 at 05:27:32PM -0500, Tom Lane wrote:
Hi,
So if Alvaro's thing works out, the shared-sequence problem becomes moot.
Probably that's a good reason not to spend time on it just yet.
I'm still alive, and I've been following this thread. Sorry for not
giving an update.
I
Alvaro Herrera [EMAIL PROTECTED] writes:
There are a bunch of error messages saying something like
cannot foo because bar
What do you think of changing those to use errdetail in addition to
errmsg?
I'm dubious that this is really an improvement...
In any case we are past string freeze for
Hello,
==
All 96 tests passed.
==
$ uname -a
Linux paer 2.4.26-64-smp #1 SMP Thu Apr 29 04:59:03 UTC 2004 parisc64 GNU/Linux
postgresql-8.0.0rc1 build on Debian GNU/Linux sid.
--
Nol Kthe noel debian.org
Debian GNU/Linux, www.debian.org
signature.asc
26 matches
Mail list logo
