Re: [HACKERS] Call for port reports
> -Original Message- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: 24 October 2003 16:38 > To: PostgreSQL-development > Subject: [HACKERS] Call for port reports > > It is time for people to report their port testing. Please > test against current CVS or beta5 and report your 'uname -a'. Cygwin == Parallel regression tests do not complete (we normally have problems with these anyway, though they do normally complete). Serial tests pass. CYGWIN_NT-5.1 pc30 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown Cygwin Win32 Client (Windows XP Pro, VC++ 6.0) C:\cygwin\usr\local\src\postgresql-7.4beta5\src>nmake /f win32.mak ALL Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. cd include if not exist pg_config.h copy pg_config.h.win32 pg_config.h cd .. cd interfaces\libpq nmake /f win32.mak Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. Building the Win32 static library... cl.exe @C:\DOCUME~1\dpage\LOCALS~1\Temp\nma02744. getaddrinfo.c ..\..\include\c.h(66) : fatal error C1083: Cannot open include file: 'strings.h' : No such file or directory NMAKE : fatal error U1077: 'cl.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~3\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop. Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > > BUT: The default CFLAGS are set by configure to -O2, although the template > > wants -O. I manually modified the CFLAGS to -O after configure. > > template/alpha has: > > case $host_cpu in > alpha*) CFLAGS="$CFLAGS -O";; # alpha has problems with -O2 > esac > > Is this not getting invoked? After further consideration, I think that the recent patch series that tried to centralize the CFLAGS handling in configure should be reverted to configure.in revision 1.293. Otherwise, it's much to complicated to handle all the special cases. There is, after all, a reason we have been forced to keep it this way all these years. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Am Sa, den 25.10.2003 schrieb Noèl Köthe um 01:17: > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > > > The current list is at: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html > > here are some build reports. Its all on Debian GNU/Linux with different > architectures: == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' [EMAIL PROTECTED]:~/pgsql$ uname -a Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux It says i686 but its AMD Opteron: [EMAIL PROTECTED]:~/pgsql$ cat /proc/cpuinfo |more processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 240 stepping: 1 cpu MHz : 1394.299 cache size : 1024 KB ... -- Noèl Köthe Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [HACKERS] Call for port reports
On Fri, Oct 24, 2003 at 11:37:32AM -0400, Bruce Momjian wrote: > It is time for people to report their port testing. Please test against > current CVS or beta5 and report your 'uname -a'. checking build system type... i386-pc-solaris2.6 checking host system type... i386-pc-solaris2.6 checking which template to use... solaris [...] checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes [...] checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes configure: using CFLAGS=-g -O2 -fno-strict-aliasing checking whether the C compiler still works... no configure: error: cannot proceed oink% gcc -v Reading specs from /usr/local/lib/gcc-lib/i386-pc-solaris2.6/2.8.1/specs gcc version 2.8.1 CFLAGS="-g -O2" ./configure --without-readline [...] == All 93 tests passed. == Kurt ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Call for port reports
On Sat, Oct 25, 2003 at 01:03:37PM +0200, Noèl Köthe wrote: > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux > > It says i686 but its AMD Opteron: Just wondering, but does it run in 32 or 64 bit mode? I have a feeling it's only 32 bit mode ... Is it compiled for the i386 or the x86_64 arch? Did you have CONFIG_X86_64=y as compile time option? Kurt ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Am Sa, den 25.10.2003 schrieb Kurt Roeckx um 13:48: > > Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux > > > > It says i686 but its AMD Opteron: > > Just wondering, but does it run in 32 or 64 bit mode? I have a > feeling it's only 32 bit mode ... Is it compiled for the i386 or > the x86_64 arch? Did you have CONFIG_X86_64=y as compile time > option? Yes, you are right. Its "only" 32bit (kernel and userland). The Debian amd64 port team is still working on 64bit packages. -- Noèl Köthe Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [HACKERS] 2-phase commit
Of course I have no time to work on it : (, but in my opinion XA interface and support for the JDBC driver is absolutely necessary. I think that 2pc will generally be used more for supporting 2pc transactions between the DB and JMS than it would be for 2pc across 2 db's. Glad to see some progress on 2PC with Postgres though. Later Rob > > The next step is going to be writing 2PC support to the JDBC driver using > the new backend commands. XA interface would be very nice too, but I'm > personally not that interested in that. Any volunteers? > > Please comment! I'd like to know what you guys think about this. Am I > heading into the right direction? > ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Bruce Momjian writes: > > > > BUT: The default CFLAGS are set by configure to -O2, although the template > > > wants -O. I manually modified the CFLAGS to -O after configure. > > > > template/alpha has: > > > > case $host_cpu in > > alpha*) CFLAGS="$CFLAGS -O";; # alpha has problems with -O2 > > esac > > > > Is this not getting invoked? > > After further consideration, I think that the recent patch series that > tried to centralize the CFLAGS handling in configure should be reverted to > configure.in revision 1.293. Otherwise, it's much to complicated to > handle all the special cases. There is, after all, a reason we have been > forced to keep it this way all these years. Remember the old code had CFLAGS="" in lots of platforms, meaning they got no optimization. It seems right now Alpha is our only problem, and it is really just a message problem because the later flags override the earlier ones. Why can't get just remove -O2 from the alpha CFLAGS line via makefile magic? Frankly, we could just do CFLAGS="-O" and be done with it because we would not be bringing in the -O2, but I would rather keep it clean and remove just -O2. I don't think going backwards is a good solution because it spreads the problem down to the templates again. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for port reports
--On Saturday, October 25, 2003 10:00:59 -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: Peter Eisentraut wrote: Bruce Momjian writes: > > BUT: The default CFLAGS are set by configure to -O2, although the > > template wants -O. I manually modified the CFLAGS to -O after > > configure. > > template/alpha has: > >case $host_cpu in > alpha*) CFLAGS="$CFLAGS -O";; # alpha has problems with -O2 >esac > > Is this not getting invoked? After further consideration, I think that the recent patch series that tried to centralize the CFLAGS handling in configure should be reverted to configure.in revision 1.293. Otherwise, it's much to complicated to handle all the special cases. There is, after all, a reason we have been forced to keep it this way all these years. Remember the old code had CFLAGS="" in lots of platforms, meaning they got no optimization. It seems right now Alpha is our only problem, and it is really just a message problem because the later flags override the earlier ones. Why can't get just remove -O2 from the alpha CFLAGS line via makefile magic? Frankly, we could just do CFLAGS="-O" and be done with it because we would not be bringing in the -O2, but I would rather keep it clean and remove just -O2. We also get -g on UnixWare cc (NOT gcc) builds, which we didn't before, which means we do NOT get optimization (UnixWare's cc doesn't like -O and -g together). LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Call for port reports
Bruce Momjian wrote: > Peter Eisentraut wrote: > > Bruce Momjian writes: > > > > > > BUT: The default CFLAGS are set by configure to -O2, although the template > > > > wants -O. I manually modified the CFLAGS to -O after configure. > > > > > > template/alpha has: > > > > > > case $host_cpu in > > > alpha*) CFLAGS="$CFLAGS -O";; # alpha has problems with -O2 > > > esac > > > > > > Is this not getting invoked? > > > > After further consideration, I think that the recent patch series that > > tried to centralize the CFLAGS handling in configure should be reverted to > > configure.in revision 1.293. Otherwise, it's much to complicated to > > handle all the special cases. There is, after all, a reason we have been > > forced to keep it this way all these years. > > Remember the old code had CFLAGS="" in lots of platforms, meaning they > got no optimization. > > It seems right now Alpha is our only problem, and it is really just a > message problem because the later flags override the earlier ones. Why > can't get just remove -O2 from the alpha CFLAGS line via makefile magic? > Frankly, we could just do CFLAGS="-O" and be done with it because we > would not be bringing in the -O2, but I would rather keep it clean and > remove just -O2. > > I don't think going backwards is a good solution because it spreads the > problem down to the templates again. In fact, another question is why this alpha test is only done in freebsd? Certainly other alpha gcc platforms must have problems with -O2? I am inclined to add something to configure.in for all alpha compiles that changes -O2 to -O. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Larry Rosenman wrote: > >> After further consideration, I think that the recent patch series that > >> tried to centralize the CFLAGS handling in configure should be reverted > >> to configure.in revision 1.293. Otherwise, it's much to complicated to > >> handle all the special cases. There is, after all, a reason we have been > >> forced to keep it this way all these years. > > > > Remember the old code had CFLAGS="" in lots of platforms, meaning they > > got no optimization. > > > > It seems right now Alpha is our only problem, and it is really just a > > message problem because the later flags override the earlier ones. Why > > can't get just remove -O2 from the alpha CFLAGS line via makefile magic? > > Frankly, we could just do CFLAGS="-O" and be done with it because we > > would not be bringing in the -O2, but I would rather keep it clean and > > remove just -O2. > We also get -g on UnixWare cc (NOT gcc) builds, which we didn't before, > which means we do NOT get optimization (UnixWare's cc doesn't like > -O and -g together). We are going to fix that, but what happens? Does the compile fail or does optimization just get turned off? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > In fact, another question is why this alpha test is only done in > freebsd? Ask that to the maintainers of the FreeBSD system compiler. > Certainly other alpha gcc platforms must have problems with -O2? > I am inclined to add something to configure.in for all alpha compiles > that changes -O2 to -O. I'm not. It's one thing if FreeBSD thinks their compiler is broken. But before I accept that gcc is broken as a whole, I want to hear from the GCC folks. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
--On Saturday, October 25, 2003 10:14:14 -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: Larry Rosenman wrote: >> After further consideration, I think that the recent patch series that >> tried to centralize the CFLAGS handling in configure should be >> reverted to configure.in revision 1.293. Otherwise, it's much to >> complicated to handle all the special cases. There is, after all, a >> reason we have been forced to keep it this way all these years. > > Remember the old code had CFLAGS="" in lots of platforms, meaning they > got no optimization. > > It seems right now Alpha is our only problem, and it is really just a > message problem because the later flags override the earlier ones. Why > can't get just remove -O2 from the alpha CFLAGS line via makefile > magic? Frankly, we could just do CFLAGS="-O" and be done with it > because we would not be bringing in the -O2, but I would rather keep > it clean and remove just -O2. We also get -g on UnixWare cc (NOT gcc) builds, which we didn't before, which means we do NOT get optimization (UnixWare's cc doesn't like -O and -g together). We are going to fix that, but what happens? Does the compile fail or does optimization just get turned off? just a warning on each compile and no optimization. LER -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Bruce Momjian writes: > > > In fact, another question is why this alpha test is only done in > > freebsd? > > Ask that to the maintainers of the FreeBSD system compiler. > > > Certainly other alpha gcc platforms must have problems with -O2? > > I am inclined to add something to configure.in for all alpha compiles > > that changes -O2 to -O. > > I'm not. It's one thing if FreeBSD thinks their compiler is broken. But > before I accept that gcc is broken as a whole, I want to hear from the GCC > folks. Oh, so it is only FreeBSD that emits that warning. Interesting. I haven't seen that error from any other platform, so you must be right. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] random access - bytea
There have been (in the past at least) plans on adding a random access interface to bytea fields. I don't find it in the todo, maybe it should be added? What kind of syntax have people thought about, to let the client read a bytea field in a random access way? I'm thinking of something like: BEGIN; SELECT id, open_bytea(bytea_field, READ_ACCESS) FROM table; ... and then the client has to access the data in the same transaction, using the ID returned by open_bytea() ... COMMIT; Would that be feasible? I think it looks like a clean solution. To me it seems that accessing the data outside a transaction would not be something we want anyway, right? Sematically it's easier to implement read access then write access. For write access to work with transactions one need for example the blocks in a bytea field to be stored with the transaction id's an stuff (I don't know these parts of pg internals well enough yet). One other thing I don't know well enough yet is the new wire protocol. To support something like above, would it need to be changed? I guess so if it wasn't designed with this in mind. -- /Dennis ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Bruce Momjian writes: > > > In fact, another question is why this alpha test is only done in > > freebsd? > > Ask that to the maintainers of the FreeBSD system compiler. > > > Certainly other alpha gcc platforms must have problems with -O2? > > I am inclined to add something to configure.in for all alpha compiles > > that changes -O2 to -O. > > I'm not. It's one thing if FreeBSD thinks their compiler is broken. But > before I accept that gcc is broken as a whole, I want to hear from the GCC > folks. How does everyone like this patch? It removes -g from non-debug compiles, and changes -O2 to -O for FreeBSD/Alpha. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 Index: configure === RCS file: /cvsroot/pgsql-server/configure,v retrieving revision 1.306 diff -c -c -r1.306 configure *** configure 22 Oct 2003 04:16:27 - 1.306 --- configure 25 Oct 2003 15:44:00 - *** *** 2384,2389 --- 2384,2392 ac_compiler_gnu=$ac_cv_c_compiler_gnu + # Strip off -g added by autoconf + CFLAGS="`echo \"$CFLAGS\" | sed 's/\( *\)-g\( *\)/\1\2/'`" + # # Read the template # Index: configure.in === RCS file: /cvsroot/pgsql-server/configure.in,v retrieving revision 1.297 diff -c -c -r1.297 configure.in *** configure.in22 Oct 2003 04:16:39 - 1.297 --- configure.in25 Oct 2003 15:44:03 - *** *** 229,234 --- 229,237 AC_PROG_CC([$pgac_cc_list]) + # Strip off -g added by autoconf + CFLAGS="`echo \"$CFLAGS\" | sed 's/\( *\)-g\( *\)/\1\2/'`" + # # Read the template # Index: src/template/freebsd === RCS file: /cvsroot/pgsql-server/src/template/freebsd,v retrieving revision 1.27 diff -c -c -r1.27 freebsd *** src/template/freebsd9 Oct 2003 22:55:46 - 1.27 --- src/template/freebsd25 Oct 2003 15:44:09 - *** *** 1,6 ! case $host_cpu in ! alpha*) CFLAGS="$CFLAGS -O";; # alpha has problems with -O2 ! esac THREAD_SUPPORT=yes NEED_REENTRANT_FUNCS=yes --- 1,10 ! # alpha has problems with -O2 ! # is FreeBSD/Alpha the only gcc Alpha that can't handle -O2? ! if test "$GCC" = yes; then ! case $host_cpu in ! alpha*) CFLAGS="`echo \"$CFLAGS\" | sed 's/\( *\)-O2\( *\)/\1-O\2/'`" ;; ! esac ! fi THREAD_SUPPORT=yes NEED_REENTRANT_FUNCS=yes ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Peter Eisentraut writes: > FreeBSD 4.8-RELEASE alpha > > BUT: The default CFLAGS are set by configure to -O2, although the template > wants -O. I manually modified the CFLAGS to -O after configure. I've committed a fix for the CFLAGS handling, and now this platform works perfectly. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for port reports
--On Saturday, October 25, 2003 18:35:06 +0200 Peter Eisentraut <[EMAIL PROTECTED]> wrote: Peter Eisentraut writes: FreeBSD 4.8-RELEASE alpha BUT: The default CFLAGS are set by configure to -O2, although the template wants -O. I manually modified the CFLAGS to -O after configure. I've committed a fix for the CFLAGS handling, and now this platform works perfectly. That commit also fixed my -g issue with UnixWare. I still have the following regression.diffs: *** ./expected/privileges.out Thu Oct 9 20:49:31 2003 --- ./results/privileges.outSat Oct 25 12:04:45 2003 *** *** 247,253 (1 row) CREATE FUNCTION testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE sql; -- fail - ERROR: permission denied for language sql SET SESSION AUTHORIZATION regressuser3; SELECT testfunc1(5); -- fail ERROR: permission denied for function testfunc1 --- 247,252 == -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
[HACKERS] Function Permissions
Hi, I really need that a FUNCTION runs allways with this creator/owner permissions, and not with the user permission. In other words, my FUNCTION must execute several procedures as POSTGRES superuser, and the tables its needs access/insert/delete/update has no permissions to normal user. Only calling my FUNCTION the normal user can do that, and never updating or deleting directly over the tables. Any idea ? -Marco Túlio OliveiraIT-Managerwww.telecontrol.com.br
Re: [HACKERS] Call for port reports
Regression testing on AIX 5 using 7.4beta5: polymorphism ... ok stats... ok == shutting down postmaster == == All 93 tests passed. == bash-2.05$ uname -a AIX sn2 1 5 0044276A4C00 checking build system type... powerpc-ibm-aix5.1.0.0 checking host system type... powerpc-ibm-aix5.1.0.0 checking which template to use... aix bash-2.05$ gcc -v Reading specs from /usr/bin/../lib/gcc-lib/powerpc-ibm-aix5.1.0.0/2.9-aix43-010414/specs gcc version 2.9-aix43-010414 Good work :) Hans -- Cybertec Geschwinde u Schoenig Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria Tel: +43/2952/30706 or +43/660/816 40 77 www.cybertec.at, www.postgresql.at, kernel.cybertec.at ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
> It is time for people to report their port testing. Please test against > current CVS or beta5 and report your 'uname -a'. > > The current list is at: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html here are some build reports. Its all on Debian GNU/Linux with different architectures: == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' [EMAIL PROTECTED]:~/pgsql$ uname -a Linux bruckner 2.4.21 #1 Don Aug 28 15:18:52 CEST 2003 ppc GNU/Linux - In file included from ../../../../src/include/storage/spin.h:50, from xlog.c:37: ../../../../src/include/storage/s_lock.h:543:2: #error This platform does not support native spinlocks. To continue the compile, rerun configure using --disable-spinlocks. However, performance will be poor. Please report this to [EMAIL PROTECTED] make[4]: *** [xlog.o] Error 1 make[4]: Leaving directory `/home/noel/pgsql/src/backend/access/transam' make[3]: *** [transam-recursive] Error 2 make[3]: Leaving directory `/home/noel/pgsql/src/backend/access' make[2]: *** [access-recursive] Error 2 make[2]: Leaving directory `/home/noel/pgsql/src/backend' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/noel/pgsql/src' make: *** [all] Error 2 [EMAIL PROTECTED]:~/pgsql$ uname -a Linux paer 2.4.20-64 #1 Fri Aug 1 23:40:10 UTC 2003 parisc64 GNU/Linux rebuild with --disable-spinlocks ... transactions ... ok random ... failed (ignored) portals ... ok ... == 92 of 93 tests passed, 1 failed test(s) ignored. == The differences that caused some tests to fail can be viewed in the file `./regression.diffs'. A copy of the test summary that you see above is saved in the file `./regression.out'. rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' [EMAIL PROTECTED]:~/pgsql$ uname -a Linux paer 2.4.20-64 #1 Fri Aug 1 23:40:10 UTC 2003 parisc64 GNU/Linux this is regression.diffs: *** ./expected/random.out Thu Feb 13 05:24:04 2003 --- ./results/random.outFri Oct 24 22:19:29 2003 *** *** 31,35 WHERE random NOT BETWEEN 80 AND 120; random ! (0 rows) --- 31,36 WHERE random NOT BETWEEN 80 AND 120; random ! 122 ! (1 row) --- == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' (sid)[EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a Linux debussy 2.4.19-netwinder #1 Thu Mar 20 03:14:34 CET 2003 armv4l GNU/Linux -- == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' [EMAIL PROTECTED]:~/pgsql$ uname -a Linux merulo 2.4.18-itanium-smp #1 SMP Sat Nov 23 01:39:07 MST 2002 ia64 GNU/Linux ... transactions ... ok random ... failed (ignored) portals ... ok ... == 92 of 93 tests passed, 1 failed test(s) ignored. == The differences that caused some tests to fail can be viewed in the file `./regression.diffs'. A copy of the test summary that you see above is saved in the file `./regression.out'. rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' (unstable)[EMAIL PROTECTED]:~/pgsql$ uname -a Linux raptor 2.4.19 #1 SMP Fri Nov 29 23:53:27 CET 2002 s390 GNU/Linux -- reports of these slower systems will follow but they need a bit more time: Linux casals 2.4.19-r4k-ip22 #1 Tue Mar 18 15:38:10 CET 2003 mips unknown Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k unknown Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux -- Noèl Köthe Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [HACKERS] Function Permissions
On Sat, Oct 25, 2003 at 15:11:06 -0200, Telecontrol Networking <[EMAIL PROTECTED]> wrote: > Hi, > > I really need that a FUNCTION runs allways with this creator/owner permissions, and > not with the user permission. > > In other words, my FUNCTION must execute several procedures as POSTGRES superuser, > and the tables its needs access/insert/delete/update has no permissions to normal > user. Only calling my FUNCTION the normal user can do that, and never updating or > deleting directly over the tables. > > Any idea ? You can use security definer clause when creating the function. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > It is time for people to report their port testing. Please test against > current CVS or beta5 and report your 'uname -a'. After the just-committed fix, Tru64 5.1 alpha is OK with both cc and gcc. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Call for port reports
Larry Rosenman writes: > *** ./expected/privileges.out Thu Oct 9 20:49:31 2003 > --- ./results/privileges.out Sat Oct 25 12:04:45 2003 > *** > *** 247,253 > (1 row) > > CREATE FUNCTION testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE > sql; -- fail > - ERROR: permission denied for language sql > SET SESSION AUTHORIZATION regressuser3; > SELECT testfunc1(5); -- fail > ERROR: permission denied for function testfunc1 > --- 247,252 That sounds extremely strange. Can you step through the privileges.sql file manually (psql single-step mode) and check what the contents of pg_language, pg_shadow, current_user, and session_user are before the misbehaving command? -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Call for port reports
Am Sa, den 25.10.2003 schrieb Noèl Köthe um 01:17: > reports of these slower systems will follow but they need a bit more time: > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k unknown Peter gave me this patch for m68k: -- src/include/port/linux.h.orig Sat Oct 25 13:45:44 2003 +++ src/include/port/linux.hSat Oct 25 12:21:41 2003 @@ -45,3 +45,8 @@ #endif +#if defined(__mc68000__) +#define HAS_TEST_AND_SET +typedef unsigned char slock_t; +#endif + == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' (unstable)[EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k GNU/Linux > Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux == All 93 tests passed. == rm regress.o make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' make[1]: Leaving directory `/home/noel/pgsql/src/test' [EMAIL PROTECTED]:~/pgsql$ uname -a Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux -- Noèl Köthe <[EMAIL PROTECTED]> Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [HACKERS] Call for port reports
Kurt Roeckx writes: > configure: using CFLAGS=-g -O2 -fno-strict-aliasing > checking whether the C compiler still works... no > configure: error: cannot proceed > oink% gcc -v > Reading specs from > /usr/local/lib/gcc-lib/i386-pc-solaris2.6/2.8.1/specs > gcc version 2.8.1 > > CFLAGS="-g -O2" ./configure --without-readline I've installed a detection logic that finds out whether -fno-strict-aliasing works. Please give it a quick run through, then we check this platform off. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
--On Saturday, October 25, 2003 22:29:04 +0200 Peter Eisentraut <[EMAIL PROTECTED]> wrote: Larry Rosenman writes: *** ./expected/privileges.out Thu Oct 9 20:49:31 2003 --- ./results/privileges.outSat Oct 25 12:04:45 2003 *** *** 247,253 (1 row) CREATE FUNCTION testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE sql; -- fail - ERROR: permission denied for language sql SET SESSION AUTHORIZATION regressuser3; SELECT testfunc1(5); -- fail ERROR: permission denied for function testfunc1 --- 247,252 That sounds extremely strange. Can you step through the privileges.sql file manually (psql single-step mode) and check what the contents of pg_language, pg_shadow, current_user, and session_user are before the misbehaving command? -- Peter Eisentraut [EMAIL PROTECTED] here ya go: Script started on Sat Oct 25 16:34:24 2003 $ psql -s reg? ?? ?? ?-U p? ?ler regression Welcome to psql 7.4beta5, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit regression=# \i privileges.sql ***(Single step mode: verify command)*** CREATE USER regressuser1; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:5: ERROR: user "regressuser1" already exists ***(Single step mode: verify command)*** CREATE USER regressuser2; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:6: ERROR: user "regressuser2" already exists ***(Single step mode: verify command)*** CREATE USER regressuser3; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:7: ERROR: user "regressuser3" already exists ***(Single step mode: verify command)*** CREATE USER regressuser4; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:8: ERROR: user "regressuser4" already exists ***(Single step mode: verify command)*** CREATE USER regressuser4; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:9: ERROR: user "regressuser4" already exists ***(Single step mode: verify command)*** CREATE GROUP regressgroup1; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:11: ERROR: group "regressgroup1" already exists ***(Single step mode: verify command)*** CREATE GROUP regressgroup2 WITH USER regressuser1, regressuser2; ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:12: ERROR: group "regressgroup2" already exists ***(Single step mode: verify command)*** ALTER GROUP regressgroup1 ADD USER regressuser4; ***(press return to proceed or enter x and return to cancel) ALTER GROUP ***(Single step mode: verify command)*** ALTER GROUP regressgroup2 ADD USER regressuser2; ***(press return to proceed or enter x and return to cancel) ALTER GROUP ***(Single step mode: verify command)*** ALTER GROUP regressgroup2 DROP USER regressuser2; ***(press return to proceed or enter x and return to cancel) ALTER GROUP ***(Single step mode: verify command)*** ALTER GROUP regressgroup2 ADD USER regressuser4; ***(press return to proceed or enter x and return to cancel) ALTER GROUP ***(Single step mode: verify command)*** SET SESSION AUTHORIZATION regressuser1; ***(press return to proceed or enter x and return to cancel) SET ***(Single step mode: verify command)*** SELECT session_user, current_user; ***(press return to proceed or enter x and return to cancel) session_user | current_user --+-- regressuser1 | regressuser1 (1 row) ***(Single step mode: verify command)*** CREATE TABLE atest1 ( a int, b text ); ***(press return to proceed or enter x and return to cancel) psql:privileges.sql:26: ERROR: relation "atest1" already exists ***(Single step mode: verify command)*** SELECT * FROM atest1; ***(press return to proceed or enter x and return to cancel) a | b ---+- 1 | two 1 | two (2 rows) ***(Single step mode: verify command)**
Re: [HACKERS] Call for port reports
On 24-okt-03, at 17:37, Bruce Momjian wrote: It is time for people to report their port testing. Please test against current CVS or beta5 and report your 'uname -a'. The current list is at: http://candle.pha.pa.us/main/writings/pgsql/sgml/supported- platforms.html -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) I had trouble compiling postgressrc/pgsql/src/interfaces/ecpg/ecpglib and compiling pgsql/src/interfaces/ecpg/compatlib. Reason was I had asked during configure to include krb5 support. After adding the -lkrb5 flag to the Makefile in these subdirectories, everyting went fine. My configure options: export JAVA_HOME=/usr export PATH=/usr/local/bin:$PATH:/Developer/Java/J2EE/apache-ant-1.5.3/bin ./configure --bindir=/usr/local/bin --mandir=/usr/local/share/man/ --enable-recode --enable-odbc --enable-syslog --enable-unicode-conversion --enable-multibyte --with-CXX --enable-python --with-java --with-krb5=/usr --with-rendezvous --with-openssl=/usr/include/openssl uname -a: Darwin albatros.nest.nl 7.0.0 Darwin Kernel Version 7.0.0: Wed Sep 24 15:48:39 PDT 2003; root:xnu/xnu-517.obj~1/RELEASE_PPC Power Macintosh powerpc -johan Johan Henselmans http://www.netsense.nl Tel: +31-20-6267538 Fax: +31-20-6273852 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Bruce Momjian wrote: > How does everyone like this patch? It removes -g from non-debug > compiles, and changes -O2 to -O for FreeBSD/Alpha. I'd be hesitant to remove -g from non-debug compiles. If something crashes, it's useful to be able to get a good stacktrace from the resulting core file. The -g option makes that possible for optimized code when compiling with gcc. Is there any way we can have configure put -g in when it detects gcc? -- Kevin Brown [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: Kurt Roeckx writes: configure: using CFLAGS=-g -O2 -fno-strict-aliasing checking whether the C compiler still works... no configure: error: cannot proceed oink% gcc -v Reading specs from /usr/local/lib/gcc-lib/i386-pc-solaris2.6/2.8.1/specs gcc version 2.8.1 CFLAGS="-g -O2" ./configure --without-readline I've installed a detection logic that finds out whether -fno-strict-aliasing works. Please give it a quick run through, then we check this platform off. I thought we'd have to do this in the end, although that is quite an old version of gcc! cheers andrew ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
After CVS update for optimization flags: Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html --- Peter Eisentraut wrote: > Bruce Momjian writes: > > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > This one is OK: > > FreeBSD 4.8-RELEASE alpha > > BUT: The default CFLAGS are set by configure to -O2, although the template > wants -O. I manually modified the CFLAGS to -O after configure. > > -- > Peter Eisentraut [EMAIL PROTECTED] > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html --- Peter Eisentraut wrote: > Bruce Momjian writes: > > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > This one is OK after the recent pthread.h patch: > > NetBSD 1.6 (GENERIC) i386 > > However, the compile pointed out that in src/interfaces/libpq/fe-auth.c > line 472, variable "cmsg" is unused; and indeed it seems to be right. > Bruce, you worked most often on the peer authentication code, so maybe you > can check that. > > -- > Peter Eisentraut [EMAIL PROTECTED] > > > ---(end of broadcast)--- > TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
I can't certify the following platform because it doesn't recognize our spinlock code. Would you run src/tools/ccsym and report back the symbols you have. Do you not have __powerpc__ defined? The actual test in s_lock.h is: #if defined(__ppc__) || defined(__powerpc__) || defined(__powerpc64__) but src/include/port/linux.h only tests for the last two --- this is a mismatch we are going to clean up for 7.5, but I need to know what your compiler defines. --- Noèl Köthe wrote: -- Start of PGP signed section. > > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > > > The current list is at: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html > > here are some build reports. Its all on Debian GNU/Linux with different > architectures: > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux bruckner 2.4.21 #1 Don Aug 28 15:18:52 CEST 2003 ppc GNU/Linux > > - > > In file included from ../../../../src/include/storage/spin.h:50, > from xlog.c:37: > ../../../../src/include/storage/s_lock.h:543:2: #error This platform does not > support native spinlocks. To continue the compile, rerun configure using > --disable-spinlocks. However, performance will be poor. Please report this to [EMAIL > PROTECTED] > make[4]: *** [xlog.o] Error 1 > make[4]: Leaving directory `/home/noel/pgsql/src/backend/access/transam' > make[3]: *** [transam-recursive] Error 2 > make[3]: Leaving directory `/home/noel/pgsql/src/backend/access' > make[2]: *** [access-recursive] Error 2 > make[2]: Leaving directory `/home/noel/pgsql/src/backend' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/home/noel/pgsql/src' > make: *** [all] Error 2 > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux paer 2.4.20-64 #1 Fri Aug 1 23:40:10 UTC 2003 parisc64 GNU/Linux > > rebuild with --disable-spinlocks > > ... > transactions ... ok > random ... failed (ignored) > portals ... ok > ... > == > 92 of 93 tests passed, 1 failed test(s) ignored. > == > > The differences that caused some tests to fail can be viewed in the > file `./regression.diffs'. A copy of the test summary that you see > above is saved in the file `./regression.out'. > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux paer 2.4.20-64 #1 Fri Aug 1 23:40:10 UTC 2003 parisc64 GNU/Linux > > this is regression.diffs: > > *** ./expected/random.out Thu Feb 13 05:24:04 2003 > --- ./results/random.outFri Oct 24 22:19:29 2003 > *** > *** 31,35 > WHERE random NOT BETWEEN 80 AND 120; >random > > ! (0 rows) > > --- 31,36 > WHERE random NOT BETWEEN 80 AND 120; >random > > ! 122 > ! (1 row) > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Would someone help me getting this persons name into SGML? No?l K?the <[EMAIL PROTECTED]> I am not sure how to transfer that encoding into SGML. > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' > (sid)[EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a > Linux debussy 2.4.19-netwinder #1 Thu Mar 20 03:14:34 CET 2003 armv4l GNU/Linux Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html > -- > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux merulo 2.4.18-itanium-smp #1 SMP Sat Nov 23 01:39:07 MST 2002 ia64 GNU/Linux Updated. > > > ... > transactions ... ok > random ... failed (ignored) > portals ... ok > ... > == > 92 of 93 tests passed, 1 failed test(s) ignored. > == > > The differences that caused some tests to fail can be viewed in the > file `./regression.diffs'. A copy of the test summary that you see > above is saved in the file `./regression.out'. > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > (unstable)[EMAIL PROTECTED]:~/pgsql$ uname -a > Linux raptor 2.4.19 #1 SMP Fri Nov 29 23:53:27 CET 2002 s390 GNU/Linux Updated. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > I can't certify the following platform because it doesn't recognize our > spinlock code. Would you run src/tools/ccsym and report back the > symbols you have. Do you not have __powerpc__ defined? The way I read his report (a little tricky to find the divisions) is that ppc has passed and parisc64 doesn't have spinlock code, which sounds a lot more credible. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for port reports
Noèl Köthe wrote: -- Start of PGP signed section. > Am Sa, den 25.10.2003 schrieb No?l K?the um 01:17: > > > reports of these slower systems will follow but they need a bit more time: > > > > Linux casals 2.4.19-r4k-ip22 #1 Tue Mar 18 15:38:10 CET 2003 mips unknown > > polymorphism ... ok > stats... ok > == shutting down postmaster == Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' > [EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a > Linux casals 2.4.19-r4k-ip22 #1 Tue Mar 18 15:38:10 CET 2003 mips GNU/Linux > > > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k unknown > > gcc -g -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations > -I../../../../src/include -D_GNU_SOURCE -c -o xlog.o xlog.c > In file included from ../../../../src/include/storage/spin.h:50, > from xlog.c:37: > ../../../../src/include/storage/s_lock.h:543:2: #error This platform does not > support native spinlocks. To continue the compile, rerun configure using > --disable-spinlocks. However, performance will be poor. Please report this to [EMAIL > PROTECTED] > make[4]: *** [xlog.o] Error 1 > make[4]: Leaving directory > `/home/noel/postgresql-cvs/pgsql/src/backend/access/transam' OK, this port has the same problem with the include/port/*.h files not matching the s_lock.h files. I knew this would bite us but we didn't want to risk a reorganization during beta. The following patch has been applied and should allow m68k to work --- please report back. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 Index: src/include/port/linux.h === RCS file: /cvsroot/pgsql-server/src/include/port/linux.h,v retrieving revision 1.35 diff -c -c -r1.35 linux.h *** src/include/port/linux.h26 Sep 2003 17:39:13 - 1.35 --- src/include/port/linux.h26 Oct 2003 00:24:27 - *** *** 43,46 --- 43,51 #define HAS_TEST_AND_SET + #elif defined(__m68k__) + typedef unsigned char slock_t; + + #define HAS_TEST_AND_SET + #endif ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > Would someone help me getting this persons name into SGML? > > No?l K?the <[EMAIL PROTECTED]> > > I am not sure how to transfer that encoding into SGML. Noèl Köthe -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Call for port reports
Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html Again, I need help converting this name to SGML. --- Hans-Jürgen Schönig wrote: > Regression testing on AIX 5 using 7.4beta5: > > > polymorphism ... ok > stats... ok > == shutting down postmaster == > > == > All 93 tests passed. > == > > > bash-2.05$ uname -a > AIX sn2 1 5 0044276A4C00 > > > checking build system type... powerpc-ibm-aix5.1.0.0 > checking host system type... powerpc-ibm-aix5.1.0.0 > checking which template to use... aix > > bash-2.05$ gcc -v > Reading specs from > /usr/bin/../lib/gcc-lib/powerpc-ibm-aix5.1.0.0/2.9-aix43-010414/specs > gcc version 2.9-aix43-010414 > > Good work :) > > Hans > > -- > Cybertec Geschwinde u Schoenig > Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria > Tel: +43/2952/30706 or +43/660/816 40 77 > www.cybertec.at, www.postgresql.at, kernel.cybertec.at > > > > ---(end of broadcast)--- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Call for port reports
Dave Page wrote: > > > > -Original Message- > > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > > Sent: 24 October 2003 16:38 > > To: PostgreSQL-development > > Subject: [HACKERS] Call for port reports > > > > It is time for people to report their port testing. Please > > test against current CVS or beta5 and report your 'uname -a'. > > Cygwin > == > > Parallel regression tests do not complete (we normally have problems > with these anyway, though they do normally complete). > > Serial tests pass. > > CYGWIN_NT-5.1 pc30 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown > Cygwin > Uh, I am not inclined to mark the port as OK if the parallel regression tests fail --- what is the cause? > Win32 Client > > > (Windows XP Pro, VC++ 6.0) > > C:\cygwin\usr\local\src\postgresql-7.4beta5\src>nmake /f win32.mak ALL > > Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 > Copyright (C) Microsoft Corp 1988-1998. All rights reserved. > > cd include > if not exist pg_config.h copy pg_config.h.win32 pg_config.h > cd .. > cd interfaces\libpq > nmake /f win32.mak > > Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 > Copyright (C) Microsoft Corp 1988-1998. All rights reserved. > > Building the Win32 static library... > > cl.exe @C:\DOCUME~1\dpage\LOCALS~1\Temp\nma02744. > getaddrinfo.c > ..\..\include\c.h(66) : fatal error C1083: Cannot open include file: > 'strings.h' > : No such file or directory > NMAKE : fatal error U1077: 'cl.exe' : return code '0x2' > Stop. > NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~3\VC98\BIN\NMAKE.EXE' : > return co > de '0x2' > Stop. I am confused why strings.h is being included because there is a test around it: #ifdef HAVE_STRINGS_H #include #endif Any ideas? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
Noèl Köthe wrote: -- Start of PGP signed section. > Am Sa, den 25.10.2003 schrieb No?l K?the um 01:17: > > > It is time for people to report their port testing. Please test against > > > current CVS or beta5 and report your 'uname -a'. > > > > > > The current list is at: > > > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html > > > > here are some build reports. Its all on Debian GNU/Linux with different > > architectures: > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux > > It says i686 but its AMD Opteron: > > [EMAIL PROTECTED]:~/pgsql$ cat /proc/cpuinfo |more > processor : 0 > vendor_id : AuthenticAMD > cpu family : 15 > model : 5 > model name : AMD Opteron(tm) Processor 240 > stepping: 1 > cpu MHz : 1394.299 > cache size : 1024 KB > ... I am confused how to handle this. Is this running in 32-bit mode? I am inclined to mention Opteron only when tested in 64-bit mode, because I think we all assume a 32-bit Opteron is the same as a standard AMD/Intel. Does uname report differently in 64-bit mode. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for port reports
I am confused by your report. I have success from Solaris kernel 5.8. I see 2.6 mentioned, and I know there is Solaris 7-9. What does uname -a show? --- Kurt Roeckx wrote: > On Fri, Oct 24, 2003 at 11:37:32AM -0400, Bruce Momjian wrote: > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > checking build system type... i386-pc-solaris2.6 > checking host system type... i386-pc-solaris2.6 > checking which template to use... solaris > [...] > checking for gcc... gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > [...] > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > configure: using CFLAGS=-g -O2 -fno-strict-aliasing > checking whether the C compiler still works... no > configure: error: cannot proceed > oink% gcc -v > Reading specs from > /usr/local/lib/gcc-lib/i386-pc-solaris2.6/2.8.1/specs > gcc version 2.8.1 > > CFLAGS="-g -O2" ./configure --without-readline > [...] > == > All 93 tests passed. > == > > > Kurt > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for port reports
Noèl Köthe wrote: -- Start of PGP signed section. > Am Sa, den 25.10.2003 schrieb Kurt Roeckx um 13:48: > > > > Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux > > > > > > It says i686 but its AMD Opteron: > > > > Just wondering, but does it run in 32 or 64 bit mode? I have a > > feeling it's only 32 bit mode ... Is it compiled for the i386 or > > the x86_64 arch? Did you have CONFIG_X86_64=y as compile time > > option? > > Yes, you are right. Its "only" 32bit (kernel and userland). The Debian > amd64 port team is still working on 64bit packages. OK, I don't think we will mention 32-bit Opteron separately --- it could probably cause confusion if we didn't mention it for all platforms. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > The following patch has been applied and should allow m68k to work --- > please report back. Won't work. Please see his last mail for the right patch. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Bruce Momjian writes: > > > In fact, another question is why this alpha test is only done in > > freebsd? > > Ask that to the maintainers of the FreeBSD system compiler. > > > Certainly other alpha gcc platforms must have problems with -O2? > > I am inclined to add something to configure.in for all alpha compiles > > that changes -O2 to -O. > > I'm not. It's one thing if FreeBSD thinks their compiler is broken. But > before I accept that gcc is broken as a whole, I want to hear from the GCC > folks. We might get more gcc -O2 alpha warning reports now that we use -O2 by default --- let's see. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Bruce Momjian writes: > Uh, I am not inclined to mark the port as OK if the parallel regression > tests fail --- what is the cause? They always have been on Cygwin. This platform just can't handle that many parallel connections. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Peter Eisentraut writes: > > > FreeBSD 4.8-RELEASE alpha > > > > BUT: The default CFLAGS are set by configure to -O2, although the template > > wants -O. I manually modified the CFLAGS to -O after configure. > > I've committed a fix for the CFLAGS handling, and now this platform works > perfectly. Your approach looks good. You decided to allow template to set the CFLAGS, and if it doesn't, make it -O2/-O. That is a very clean approach. I had the idea of layering the flags so template would only _add_ to CFLAGS, but your way is clearer. One other idea would be to set CFLAGS to "" before including template, and just test to see if it is still "" after --- that might be cleaner than saving the original value and comparing. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html --- Peter Eisentraut wrote: > Bruce Momjian writes: > > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > After the just-committed fix, Tru64 5.1 alpha is OK with both cc and gcc. > > -- > Peter Eisentraut [EMAIL PROTECTED] > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html m68k patch already applied. --- Noèl Köthe wrote: -- Start of PGP signed section. > Am Sa, den 25.10.2003 schrieb No?l K?the um 01:17: > > > reports of these slower systems will follow but they need a bit more time: > > > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k unknown > > Peter gave me this patch for m68k: > > -- src/include/port/linux.h.orig Sat Oct 25 13:45:44 2003 > +++ src/include/port/linux.hSat Oct 25 12:21:41 2003 > @@ -45,3 +45,8 @@ > > #endif > > +#if defined(__mc68000__) > +#define HAS_TEST_AND_SET > +typedef unsigned char slock_t; > +#endif > + > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' > (unstable)[EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k GNU/Linux > > > Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux > > > > -- > > No?l K?the <[EMAIL PROTECTED]> > > Debian GNU/Linux, www.debian.org -- End of PGP section, PGP failed! -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html m68k patch already applied. --- Noèl Köthe wrote: -- Start of PGP signed section. > Am Sa, den 25.10.2003 schrieb No?l K?the um 01:17: > > > reports of these slower systems will follow but they need a bit more time: > > > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k unknown > > Peter gave me this patch for m68k: > > -- src/include/port/linux.h.orig Sat Oct 25 13:45:44 2003 > +++ src/include/port/linux.hSat Oct 25 12:21:41 2003 > @@ -45,3 +45,8 @@ > > #endif > > +#if defined(__mc68000__) > +#define HAS_TEST_AND_SET > +typedef unsigned char slock_t; > +#endif > + > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/postgresql-cvs/pgsql/src/test' > (unstable)[EMAIL PROTECTED]:~/postgresql-cvs/pgsql$ uname -a > Linux crest 2.4.20 #1 Wed Mar 5 01:39:17 EST 2003 m68k GNU/Linux > > > Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux escher 2.4.22 #2 Sat Sep 6 18:23:54 CEST 2003 alpha GNU/Linux > > > > -- > > No?l K?the <[EMAIL PROTECTED]> > > Debian GNU/Linux, www.debian.org -- End of PGP section, PGP failed! -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Call for port reports
Kevin Brown wrote: > Bruce Momjian wrote: > > How does everyone like this patch? It removes -g from non-debug > > compiles, and changes -O2 to -O for FreeBSD/Alpha. > > I'd be hesitant to remove -g from non-debug compiles. If something > crashes, it's useful to be able to get a good stacktrace from the > resulting core file. The -g option makes that possible for optimized > code when compiling with gcc. > > Is there any way we can have configure put -g in when it detects gcc? Even without -g, you still get function names in the backtrace. The only time you don't get this is when you strip the executable. -g adds the function line number. configure --enable-debug will use -g for the compile, and with optimization. We aren't changing that, we are only preventing -g by default. Most installers are stripping the executables anyway --- this might discourage them from doing that. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for port reports
Noèl Köthe wrote: -- Start of PGP signed section. > > > It is time for people to report their port testing. Please test against > > current CVS or beta5 and report your 'uname -a'. > > > > The current list is at: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html > > here are some build reports. Its all on Debian GNU/Linux with different > architectures: > > == > All 93 tests passed. > == > > rm regress.o > make[2]: Leaving directory `/home/noel/pgsql/src/test/regress' > make[1]: Leaving directory `/home/noel/pgsql/src/test' > [EMAIL PROTECTED]:~/pgsql$ uname -a > Linux bruckner 2.4.21 #1 Don Aug 28 15:18:52 CEST 2003 ppc GNU/Linux Ports list updated: http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I can't certify the following platform because it doesn't recognize our
> > spinlock code. Would you run src/tools/ccsym and report back the
> > symbols you have. Do you not have __powerpc__ defined?
>
> The way I read his report (a little tricky to find the divisions) is that
> ppc has passed and parisc64 doesn't have spinlock code, which sounds a
> lot more credible.
Oh, I see now --- sorry.
Wow, I looked in hpux.h and saw:
#if defined(__hppa)
#define HAS_TEST_AND_SET
typedef struct
{
int sema[4];
} slock_t;
#ifndef BYTE_ORDER
#define BYTE_ORDER BIG_ENDIAN
#endif
and I see in s_lock.h:
#if defined(__hppa)
/*
* HP's PA-RISC
*
* Note that slock_t on PA-RISC is a structure instead of char
* (see include/port/hpux.h).
*
* a "set" slock_t has a single word cleared. a "clear" slock_t has
* all words set to non-zero. tas() is in tas.s
*/
#define S_UNLOCK(lock) \
do { \
volatile slock_t *lock_ = (volatile slock_t *) (lock); \
lock_->sema[0] = -1; \
lock_->sema[1] = -1; \
lock_->sema[2] = -1; \
lock_->sema[3] = -1; \
} while (0)
#define S_LOCK_FREE(lock) ( *(int *) (((long) (lock) + 15) & ~15) != 0)
#endif /* __hppa */
Can Linux handle this? Can you copy the stuff from hpux.h and see if
that works for Linux?
We can't mark this port as working unless we have spinlocks.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [HACKERS] Call for port reports
Thanks. SGML updated. --- Peter Eisentraut wrote: > Bruce Momjian writes: > > > Would someone help me getting this persons name into SGML? > > > > No?l K?the <[EMAIL PROTECTED]> > > > > I am not sure how to transfer that encoding into SGML. > > Noèl Köthe > > -- > Peter Eisentraut [EMAIL PROTECTED] > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for port reports
Peter Eisentraut wrote: > Bruce Momjian writes: > > > The following patch has been applied and should allow m68k to work --- > > please report back. > > Won't work. Please see his last mail for the right patch. Got it --- applied --- __mc68000__. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for port reports
Dave Page wrote: > > > > -Original Message- > > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > > Sent: 24 October 2003 16:38 > > To: PostgreSQL-development > > Subject: [HACKERS] Call for port reports > > > > It is time for people to report their port testing. Please > > test against current CVS or beta5 and report your 'uname -a'. > > Cygwin > == > > Parallel regression tests do not complete (we normally have problems > with these anyway, though they do normally complete). > > Serial tests pass. > > CYGWIN_NT-5.1 pc30 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown > Cygwin Cygwin marked as completed by Peter. Thanks. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for port reports
Impressive. We already have a long list of supported 7.4 platforms, all in 24 hours! http://momjian.postgresql.org/main/writings/pgsql/sgml/supported-platforms.html -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Isolation levels READ UNCOMMITTED and REPEATABLE READ
Added to TODO: * Allow more ISOLATION LEVELS to be accepted, but issue a warning for them --- Tom Lane wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > I think we could allow users to set the transaction isolation level to > > READ UNCOMMITTED or REPEATABLE READ and internally behave like READ > > COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow > > this: > > My reading is that the spec *requires* this. We have not done it > because there was some feeling that people would be confused if the > isolation levels appeared to exist but didn't really work as they > expected. But a notice or something could help address that concern. > > regards, tom lane > > ---(end of broadcast)--- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Database Kernels and O_DIRECT
Tom Lane wrote: > James Rogers <[EMAIL PROTECTED]> writes: > > If we suddenly wanted to optimize Postgres for performance the way > > Oracle does, we would be a lot more keen on the O_DIRECT approach. > > This isn't ever going to happen, for the simple reason that we don't > have Oracle's manpower. You are blithely throwing around the phrase > "database kernel" like it would be a small simple project. In reality > you are talking about (at least) implementing our own complete > filesystem, and then doing it over again on every platform we want to > support, and then after that, optimizing it to the point of actually > being enough better than the native facilities to have been worth the > effort. I cannot conceive of that happening in a Postgres project that > even remotely resembles the present reality, because we just don't have > the manpower; and what manpower we do have is better spent on other > tasks. We have other things to do than re-invent the operating system > wheel. Improving the planner, for example. One question is what a database kernel would look like? Would it basically mean just taking our existing portability code, such as for shared memory, and moving it into a separate libary with its own API? Don't we almost have that already? I am just confused what would be different? I think the only major difference I have heard is to bypass the OS file system and memory management. We already bypass most of the memory management by using palloc. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 compatibility question
Tatsuo Ishii wrote: > > I've been pushing this agenda for a few releases now, but some people have > > been, er, boycotting it. I think, too, that release notes *must* be > > written incrementally at the same time that the feature change is made. > > This is the only way we can get accurate and complete release notes, and > > the descriptions could even include some context, some motivations, etc. > > We have release cycles of 10 months, and there is no way we can make > > sensible release notes by gathering individual commit messages over that > > period of time. Heck, ECPG has a full Informix compatibility mode and > > there is no mention of that anywhere, because there was no commit "Add > > Informix mode." > > > > I suggest we just do it like the documentation: If you don't document it, > > it doesn't exist. If you don't write a line for the release notes, it > > doesn't exist either. > > I tend to agree it. For every release I and my colleague have been > working on creating detailed release notes (of course in Japanese), > otherwise we cannot tell people what are changed, added or fixed since > there is little info in the official release note. This is painful > since we have to dig into the mail archives and cvs commit messages to > look for what each item of the official release note actually > means. These work take at least 2 to 3 weeks with several people > involved. The hardest part is what are fixed. The only useful > information seems to be the cvs commit messages, however typical > messages are something like "see recent discussions in the mail > archive for more details". This is not very helpful at least for > me. Once I proposed that we add a sequence number to each mail and the > commit messages point to the number. This way we could easily trace > what are the bug report and what are the actual intention for the > fix. For some reason noboy was interested in. Maybe this is due to > "coulture gap"... (In Japan giving a sequence number to each mail in > mailing lists is quite common). OK, if Tatsuo and SRA are having problems, I have to address it. I can supply a more detailed list to Tatsuo/SRA, or I can beef up the release notes to contain more information. Seems some in the community would like to have this detail so I might as well do it and have it in the official docs. One idea would be to add a section at the bottom of the release notes that goes into detail on changes listed in the release notes above --- that way, people can still skim the 300-line release notes, and if they want detailed information about the optimizer changes or subtle pg_dump fixes, that will be at the bottom. How does that sound? I can start on this for 7.4 next week. It basically means going through the CVS logs again and pulling out additional details. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Timestamp docs weirdness
OK, do we want to put back the mention of these in the release notes? The non-zulu ones sound pretty strange to me and might be better left undocumented. --- Marcus B?rger wrote: > Hello Christopher, > > Wednesday, October 22, 2003, 10:21:02 AM, you wrote: > > >>>What in the heck is 'zulu', 'allballs' or 'z'??? > >> > >> > >> 'allballs' probably alludes to the visual appearance of '00:00:00'. 'z' > >> and 'zulu' should be time zones equivalent (or similar?) to UTC or GMT > >> ((US?) military jargon). > > > But they don't work... > > Only the combination of both doesn't work: > template1=# select 'allballs'::timetz; >timetz > - > 00:00:00+00 > (1 row) > > template1=# select '0:0:0 z'::timetz; >timetz > - > 00:00:00+00 > (1 row) > > template1=# select '0:0:0 zulu'::timetz; >timetz > - > 00:00:00+00 > (1 row) > > template1=# select 'allballs'::timetz; >timetz > - > 00:00:00+00 > (1 row) > > template1=# select 'allballs z'::timetz; > ERROR: Bad time external representation 'allballs z' > template1=# select 'allballs zulu'::timetz; > ERROR: Bad time external representation 'allballs zulu' > > Your problem is using 'time' which doesn't know time zones. > > -- > Best regards, > Marcusmailto:[EMAIL PROTECTED] > > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > >http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] integer ceiling in LIMIT and OFFSET
Rod Taylor wrote: -- Start of PGP signed section. > On Wed, 2003-10-22 at 04:01, Christopher Kings-Lynne wrote: > > Hi guys, > > > > What is the limit on the number of rows in a PostgreSQL table? If it's > > more than MAXINT, we have a problem: > > > > phppgadmin# select * from test limit 2147483648; > > ERROR: integer out of range > > > > Same problem with OFFSET. > > I see you're point, but nobody is going to be interested in the first 2 > billion rows of a table without using a cursor and having some other > process do the math in the background. > > That said, perhaps the TODO for changing LIMIT / OFFSET to be expression > based should also mention bumping them to int8. Added to TODO: * Change LIMIT/OFFSET to use int8 -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] 7.4 compatibility question
> Tatsuo Ishii wrote: > > > I've been pushing this agenda for a few releases now, but some people have > > > been, er, boycotting it. I think, too, that release notes *must* be > > > written incrementally at the same time that the feature change is made. > > > This is the only way we can get accurate and complete release notes, and > > > the descriptions could even include some context, some motivations, etc. > > > We have release cycles of 10 months, and there is no way we can make > > > sensible release notes by gathering individual commit messages over that > > > period of time. Heck, ECPG has a full Informix compatibility mode and > > > there is no mention of that anywhere, because there was no commit "Add > > > Informix mode." > > > > > > I suggest we just do it like the documentation: If you don't document it, > > > it doesn't exist. If you don't write a line for the release notes, it > > > doesn't exist either. > > > > I tend to agree it. For every release I and my colleague have been > > working on creating detailed release notes (of course in Japanese), > > otherwise we cannot tell people what are changed, added or fixed since > > there is little info in the official release note. This is painful > > since we have to dig into the mail archives and cvs commit messages to > > look for what each item of the official release note actually > > means. These work take at least 2 to 3 weeks with several people > > involved. The hardest part is what are fixed. The only useful > > information seems to be the cvs commit messages, however typical > > messages are something like "see recent discussions in the mail > > archive for more details". This is not very helpful at least for > > me. Once I proposed that we add a sequence number to each mail and the > > commit messages point to the number. This way we could easily trace > > what are the bug report and what are the actual intention for the > > fix. For some reason noboy was interested in. Maybe this is due to > > "coulture gap"... (In Japan giving a sequence number to each mail in > > mailing lists is quite common). > > OK, if Tatsuo and SRA are having problems, I have to address it. I can > supply a more detailed list to Tatsuo/SRA, or I can beef up the release > notes to contain more information. Seems some in the community would > like to have this detail so I might as well do it and have it in the > official docs. One idea would be to add a section at the bottom of the > release notes that goes into detail on changes listed in the release > notes above --- that way, people can still skim the 300-line release > notes, and if they want detailed information about the optimizer changes > or subtle pg_dump fixes, that will be at the bottom. > > How does that sound? I can start on this for 7.4 next week. It > basically means going through the CVS logs again and pulling out > additional details. Sounds good. However this kind of information could become huge and I am afraid it does not suite well in the official docs in the source tree. I think putiing it in somewhere in a web site (maybe http://developer.postgresql.org/?) might be more appropreate. What do you think? -- Tatsuo Ishii ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.4 compatibility question
Tatsuo Ishii wrote: > > OK, if Tatsuo and SRA are having problems, I have to address it. I can > > supply a more detailed list to Tatsuo/SRA, or I can beef up the release > > notes to contain more information. Seems some in the community would > > like to have this detail so I might as well do it and have it in the > > official docs. One idea would be to add a section at the bottom of the > > release notes that goes into detail on changes listed in the release > > notes above --- that way, people can still skim the 300-line release > > notes, and if they want detailed information about the optimizer changes > > or subtle pg_dump fixes, that will be at the bottom. > > > > How does that sound? I can start on this for 7.4 next week. It > > basically means going through the CVS logs again and pulling out > > additional details. > > Sounds good. However this kind of information could become huge and I > am afraid it does not suite well in the official docs in the source > tree. I think putiing it in somewhere in a web site (maybe > http://developer.postgresql.org/?) might be more appropreate. > What do you think? Yes, I had thought about that --- I put something about migrating to 7.3 on a web page and put the URL in the release notes, and the URL kept becoming invalid as they changed web configurations. I am afraid we have to keep this in CVS so we don't lose it over time. It could be huge. Current release notes for 7.4 is around 500 lines. I think I could do this in another 500 lines. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] random access - bytea
Dennis Bjorklund wrote: There have been (in the past at least) plans on adding a random access interface to bytea fields. I don't find it in the todo, maybe it should be added? First do this: ALTER TABLE foo ALTER COLUMN foo_bytea SET STORAGE EXTERNAL; see: http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=sql-altertable.html Then do: UPDATE foo SET foo_bytea = foo_bytea || ''; That will modify the bytea column so that it is stored uncompressed in the TOAST table. Now, simply use substr() to grab any random chunk: SELECT substr(foo_bytea, 2, 100) from foo where foo_id = 42; When TOASTed columns are stored uncompressed, substring will grab just the needed chunks from the TOAST table directly. In contrast, when the field is stored compressed, it grabs the entire thing, uncompresses it, then gets the piece you asked for. HTH, Joe ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] random access - bytea
On Sat, 25 Oct 2003, Joe Conway wrote: > That will modify the bytea column so that it is stored uncompressed in > the TOAST table. > > Now, simply use substr() to grab any random chunk: > SELECT substr(foo_bytea, 2, 100) from foo where foo_id = 42; This would imply that every little read would have to do a scan on a table to find the row and then to perform the substr. An open command can be optimized a lot more, for example to cache entries that have been opened so that it's fast to read the next 1kb or whatever you want. Also, the above does not solve writes at all which can also be made transaction safe and fast with a better api where you can update a part of a field. The above is not really a replacement of the current lo-objects. -- /Dennis ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] cvs
What is the policy for getting cvs access? The translation work
would be so much easier of one could get permission to update
the po files directly. For example, the pg_dump file now got one
string that is not updated, to fix that I have to perfom this steps:
fetch file (cvs co or other method)
update the string
create diff, or in the case of po-files it's often easier to just
send the whole thing since there are a lot of stupid line
numbers that have always changed making patches big anyway.
write mail and attach file
while(!commited) { check for commit and poke commiter if needed }
My prefered way to work is to continiously update the translations when
needed. If someone adds a comma to a string, I have to perform the same
change to the translated string. It has to be an easy task if I'm going to
stay on top of the translation, and not having to spend 3 full days just
before release.
I'd be happy to promise to only update the po-files. Alla commits are
tracable and revertable anyway, so what is the problem?
--
/Dennis
---(end of broadcast)---
TIP 8: explain analyze is your friend
