Re: [HACKERS] Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)
Olivier PRENANT wrote: Larry Rosenman wrote: I am inclined to think yes. It would prevent uglification of the code by not having to special-case Unixware. However, I was able to read the libc sources to confirm thread-safety. Because you can not see the source, would you try a threaded program and see if calls to getpwuid from different threads return different pointer values? It won't prove anything on MY box, as it is a UNIPROCESSOR, so the threads won't be dispatched at the same time. I have 2 bi-pro machines here both running unixware 7.1.3 I can make tests if you want It's ok to assume thread-safety, as the SCO developer (Kean Johnston) asked the threads guys, and he said that the libc stuff is thread-safe so they don't have to have 2 different versions in libc. LER If any one can write a program that can prove anything (I can't), I'm willing to test it here on a bi-pro (bi PIII and bi-XEON with JT enabled) running uw713. Maybe it will end the discussion and make a point in either way. So that we (you?) can move on with the other unixware patches. ---(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] Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)
Larry Rosenman wrote: --On Tuesday, September 02, 2003 11:35:25 -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: Larry Rosenman wrote: --On Tuesday, September 02, 2003 11:20:14 -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: > Peter Eisentraut wrote: >> Lee Kindness writes: >> >> > You don't... and you simply shouldn't care. If there is a_r version >> > available then we should use it - even if the plain version is >> > "safe". >> >> The problem with this is that the automatic determination (in >> configure) whether there is a xxx_r() version is, in general, >> fragile. We cannot rely on configure saying that xxx_r() doesn't >> exist, so the plain xxx() should be good enough. Else, we'd be >> shipping claimed-to-be-thread-safe libraries that might trigger bugs >> that will be hard to track down. >> >> I don't see any other solution than keeping a database of NEED_XXX_R >> for each platform and then requiring these functions to show up >> before we declare a library to be thread-safe. So far we're only >> dealing with three functions, to it should be doable. > > Right. We can't assume because a *_r function is missing that the > normal function is thread-safe. So, given that UnixWare doesn't have gethostbyname_r and strerror_r, but does have getpwuid_r, will y'all declare that UnixWare has thread-safety? My vote is YES. I am inclined to think yes. It would prevent uglification of the code by not having to special-case Unixware. However, I was able to read the libc sources to confirm thread-safety. Because you can not see the source, would you try a threaded program and see if calls to getpwuid from different threads return different pointer values? It won't prove anything on MY box, as it is a UNIPROCESSOR, so the threads won't be dispatched at the same time. I have 2 bi-pro machines here both running unixware 7.1.3 I can make tests if you want It's ok to assume thread-safety, as the SCO developer (Kean Johnston) asked the threads guys, and he said that the libc stuff is thread-safe so they don't have to have 2 different versions in libc. LER ---(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
[HACKERS] Strange crash with pg_dump
Hi everyone. Environment: OS: UW 713 PG: 7.3.2 I've been banging my head for a few weeks on this one and could'nt find any answer: pg_dump is crashing with SIGSEGV before it connects to database. I've re-compiled with --enable-debug and --enable-cassert and even that did'nt help. this is gdb output not showing much: Script started on Mon Mar 3 13:26:51 2003 ~ 13:26:51: gdb /usr/local/pgsql/bin/pg_dump /archives/dbbackup/core.28913 GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-unknown-sysv5UnixWare7.1.3"... Core was generated by `pg_dump forums_ahe'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/pgsql/lib/libpq.so.3...done. Loaded symbols for /usr/local/pgsql/lib/libpq.so.3 Reading symbols from /usr/lib/libz.so...done. Loaded symbols for /usr/lib/libz.so Reading symbols from /usr/local/lib/libreadline.so.3...done. Loaded symbols for /usr/local/lib/libreadline.so.3 Reading symbols from /usr/lib/libresolv.so.2...done. Loaded symbols for /usr/lib/libresolv.so.2 Reading symbols from /usr/lib/libsocket.so.2...done. Loaded symbols for /usr/lib/libsocket.so.2 Reading symbols from /usr/lib/libnsl.so.1...done. Loaded symbols for /usr/lib/libnsl.so.1 Reading symbols from /usr/lib/libdl.so.1... warning: Lowest section in /usr/lib/libdl.so.1 is .hash at 00a0 done. Loaded symbols for /usr/lib/libdl.so.1 Reading symbols from /usr/lib/libm.so.1...done. Loaded symbols for /usr/lib/libm.so.1 Reading symbols from /usr/lib/libc.so.1...done. Loaded symbols for /usr/lib/libc.so.1 Reading symbols from /usr/lib/ns.so.1...done. Loaded symbols for /usr/lib/ns.so.1 #0 0xbffa3dd0 in flushsmall () from /usr/lib/libc.so.1 (gdb) bt #0 0xbffa3dd0 in flushsmall () from /usr/lib/libc.so.1 #1 0x0030 in ?? () (gdb) ~ 13:27:44: exit script done on Mon Mar 3 13:27:48 2003 If I vacuum the databse it starts to work again until the script doing backup runs then pg_dump crashes again. This is a test system so databases are not even accessed! They are pulled from the real server running 7.2.3 with pg_dumpall (the 7.3 one) -h server -c|psql template1 It doesn't seem to be a database issue because it used to crash on another one. While I'm at it : what is the procedure to remove template1 and replace it by template0 after a reload? It doesn't seem right to me that pg_dumpall replace template1 but maybe I'm wrong on this one. Thanks for your tim and help -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] problems with configure
Hi every one, I'm having a weird time compiling postgresql 7.3.x on uw 713. No matter what I put after .configure, it's not taken into account :? Works fine on uw 711 the neat exemple is that it can't find readline even with --with-includes=/usr/local/include --with-java doesn't event check for ant and so on. So far, I've tried with sh, ksh and bash to no avail. Just can't uindertsand. What am I doing wrong?? the paths are ok and I succeeded a few weeks ago ... What could cause? TIA -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] New Portal in Place, DNS switched ...
Hi Marc, Just tested it! it seemes that the address for the french flag is wrong: http://www.fr.postgresql.org/www.postgresql.org instead of just www.fr.postgresql.org. Regards, On Sun, 5 Jan 2003, Marc G. Fournier wrote: > Date: Sun, 5 Jan 2003 01:51:58 + (UTC) > From: Marc G. Fournier <[EMAIL PROTECTED]> > Newsgroups: comp.databases.postgresql.hackers > Subject: Re: New Portal in Place, DNS switched ... > > On Sun, 5 Jan 2003, Justin Clift wrote: > > > www.postgresql.org/doc -> www.ca.postgresql.org/users-lounge/ > > If we can avoid it, let's ... if I recall correctly, we originally set > that up in order to get around some issues we had with originally moving > over to the new site way way back ... > > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Problems with 7.3.1
Tom, I've re-done all tests and I confirm that it works ok on the root disk but not on the others. Ok, this is an old machine but, should I send you a tgz of th pgsql directory if you want to analyse the files? Maybe my strange system triggers an unknown bug? Regards, On Fri, 27 Dec 2002, Tom Lane wrote: > Date: Fri, 27 Dec 2002 11:34:01 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Problems with 7.3.1 > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > I tried postgresql 7.3 and 7.3.1 and they both fail regressin when > > creating plpgsql language. However, when installed, createlang plpgsql > > template1 work like a charm. > > Interesting. Would you try another test: now that you've completed the > installation, does "make check" work? I am wondering if "make check" > was picking up the wrong version of plpgsql.so, ie, the one from your > pre-7.3 installation. (I'm not very clear on how a wrong version of > plpgsql.so would result in the particular failure you observed, but this > is the only theory I can think of right now...) > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Problems with 7.3.1
Hi Tom Here are some news and tests I did and am still doing: 1) there is no previous installation so that can't be a library problem (good thing!) 2) My tests and compiles are running on data disk ibm 18G uw and fail. I ended up intalling on the root disk and installcheck did work ok!! I just finish low reformating the 2 data disk , recreate file systems and reload. Make check stiil fails at the same point, driver shows no disk error... Anymore idea? Regards, On Fri, 27 Dec 2002, Tom Lane wrote: > Date: Fri, 27 Dec 2002 11:34:01 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Problems with 7.3.1 > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > I tried postgresql 7.3 and 7.3.1 and they both fail regressin when > > creating plpgsql language. However, when installed, createlang plpgsql > > template1 work like a charm. > > Interesting. Would you try another test: now that you've completed the > installation, does "make check" work? I am wondering if "make check" > was picking up the wrong version of plpgsql.so, ie, the one from your > pre-7.3 installation. (I'm not very clear on how a wrong version of > plpgsql.so would result in the particular failure you observed, but this > is the only theory I can think of right now...) > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Problems with 7.3.1
Tom, I'm puzzled! I tried postgresql 7.3 and 7.3.1 and they both fail regressin when creating plpgsql language. However, when installed, createlang plpgsql template1 work like a charm. Could it be because the machine is slow (and disks too!) Regards, On Thu, 26 Dec 2002, Tom Lane wrote: > Date: Thu, 26 Dec 2002 13:44:51 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Problems with 7.3.1 > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > Compile works ok however make check fails wile creating pl/pgsql with : > > WARNING: bt_getroot[pg_proc_proname_nsp_index]: fixing root page > > ERROR: bt_fixroot: not valid old root page. > > Wow. Is the behavior reproducible? How about if you go ahead and > install, and do a plain "make installcheck" (or even just try a manual > createlang in a fresh database)? > > That code thinks it is dealing with a concurrent index root page split, > but there couldn't be any concurrent operations happening during the > create-plpgsql step of a regression test run. Can you step through > _bt_getroot() (it's in src/backend/access/nbtree/nbtpage.c) and figure > out exactly how it's getting confused? > > If the behavior is reproducible I'm inclined to suspect a compiler bug; > it's hard to see how _bt_getroot could get so confused otherwise. > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Problems with 7.3.1
Dear Tom On Thu, 26 Dec 2002, Tom Lane wrote: > Date: Thu, 26 Dec 2002 13:44:51 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Problems with 7.3.1 > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > Compile works ok however make check fails wile creating pl/pgsql with : > > WARNING: bt_getroot[pg_proc_proname_nsp_index]: fixing root page > > ERROR: bt_fixroot: not valid old root page. > > Wow. Is the behavior reproducible? How about if you go ahead and > install, and do a plain "make installcheck" (or even just try a manual > createlang in a fresh database)? Yes it is! each time, even with make install make installcheck > > That code thinks it is dealing with a concurrent index root page split, > but there couldn't be any concurrent operations happening during the > create-plpgsql step of a regression test run. Can you step through > _bt_getroot() (it's in src/backend/access/nbtree/nbtpage.c) and figure > out exactly how it's getting confused? > I will, after diner! > If the behavior is reproducible I'm inclined to suspect a compiler bug; > it's hard to see how _bt_getroot could get so confused otherwise. > AFAIK, the 711b compiler was buggy, but 712 was ok and 713 should at least be s good as 712 (larry should confirm that!) In the mean time, I'll try with 7.3 and 7.2.3 regards, > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] Problems with 7.3.1
Hi every one and happy Xmas. Hope you can still answer that one. Waiting for my brand you server, I've installed an old bi-PII 300 unser unixware 713 and trying postgresql 7.3.1 with it. Compile works ok however make check fails wile creating pl/pgsql with : WARNING: bt_getroot[pg_proc_proname_nsp_index]: fixing root page ERROR: bt_fixroot: not valid old root page. What could be causing that (I've tested on uw 711 with no problem) Many thanks in advance -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
Many thanks Larry, Sorry I had omited the -Xb (no secret dance) in my report... On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 15:17:28 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: Peter Eisentraut <[EMAIL PROTECTED]>, Olivier PRENANT <[EMAIL PROTECTED]> > Cc: Tom Lane <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > > > --On Thursday, November 07, 2002 22:21:56 +0100 Peter Eisentraut > <[EMAIL PROTECTED]> wrote: > > > Olivier PRENANT writes: > > > >> I don't mind having CFLAGS=-Xb though, done it for php already... > >> By everyone says this should go off so.. > > > > The idea of the platform testing is not to determine whether you can > > compile PostgreSQL after performing a secret dance. If it doesn't compile > > with the default options, please don't report it as supported. > It DOES compile out of the box now on 8.0.0(7.1.2) and 7.1.3. Apparently a > compiler > fix between the 7.1.1b FS and 7.1.2. > > The -Xb switch is NOT a secret dance. It's needed for LOTS of open source > stuff. > > See the discussion from the Caldera folks last week. > > Tom's fix fixed the defaults for 7.1.2+ > > > > > > -- > > Peter Eisentraut [EMAIL PROTECTED] > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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: [PORTS] [HACKERS] PostgreSQL supported platform report and a
Haha!!! It passes (b4) on 800 and not on uw 711.. Larry, should I install 800 SDK on 711? On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 10:45:13 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Tom Lane <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > cc -O -g -I../../../../src/include -I/usr/local/include -c -o tuplesort.o > tuplesort.c > UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled > > It still passes here. I really wonder if they fixed something in the 4.1 > compiler. IIRC > the 7.1.1b compiler is 4.0. > > Truly wierd. > > LER > > > --On Thursday, November 07, 2002 17:40:24 +0100 Olivier PRENANT > <[EMAIL PROTECTED]> wrote: > > > What's FS, it(s the 7.1.1b compiler yes. > > > > I don't mind having CFLAGS=-Xb though, done it for php already... > > By everyone says this should go off so.. > > > > Regards > > On Thu, 7 Nov 2002, Larry Rosenman wrote: > > > >> Date: Thu, 07 Nov 2002 10:37:36 -0600 > >> From: Larry Rosenman <[EMAIL PROTECTED]> > >> To: [EMAIL PROTECTED], Tom Lane <[EMAIL PROTECTED]> > >> Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > >> [EMAIL PROTECTED] > >> Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and > >> a > >> > >> It **LOOKS** right. I'm about to double check it on 7.1.3. > >> > >> Olivier, is this the 7.1.1b FS Compiler? > >> > >> I wonder if a bug fix made it in... > >> > >> Wierd. > >> > >> > >> > >> --On Thursday, November 07, 2002 17:34:49 +0100 Olivier PRENANT > >> <[EMAIL PROTECTED]> wrote: > >> > >> > I see the latter in both b4 and b5! > >> > > >> > I've just relaunched my mirroring procedure and it did'nt pick another > >> > b4 or b5! > >> > > >> > What happens?? > >> > > >> > Regards, > >> > On Thu, 7 Nov 2002, Tom Lane wrote: > >> > > >> >> Date: Thu, 07 Nov 2002 11:26:42 -0500 > >> >> From: Tom Lane <[EMAIL PROTECTED]> > >> >> To: [EMAIL PROTECTED] > >> >> Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie > >> >> <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > >> >> [EMAIL PROTECTED] > >> >> Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report > >> >> and a > >> >> > >> >> Olivier PRENANT <[EMAIL PROTECTED]> writes: > >> >> > *WHAT??** > >> >> > this directory has hust been created by de-taring > >> >> > postgresql-7.3b5.tar.gz from my own mirror dated nov 6 20:04... > >> >> > >> >> Well, there's something darn weird here. Is > >> >> src/backend/utils/sort/tuplesort.c version 1.28 or 1.29? At line > >> >> 1838, do you see > >> >> inline int32 > >> >> ApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind kind, > >> >> or > >> >> static inline int32 > >> >> inlineApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind > >> >> kind, > >> >> > >> >> regards, tom lane > >> >> > >> > > >> > -- > >> > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > >> > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > >> > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > >> > FRANCE Email: [EMAIL PROTECTED] > >> > -- > >> > --- - Make your life a dream, make your dream a reality. (St > >> > Exupery) > >> > >> > >> > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > - > > - Make your life a dream, make your dream a reality. (St Exupery) > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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: [PORTS] [HACKERS] PostgreSQL supported platform report and a
What's FS, it(s the 7.1.1b compiler yes. I don't mind having CFLAGS=-Xb though, done it for php already... By everyone says this should go off so.. Regards On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 10:37:36 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], Tom Lane <[EMAIL PROTECTED]> > Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > It **LOOKS** right. I'm about to double check it on 7.1.3. > > Olivier, is this the 7.1.1b FS Compiler? > > I wonder if a bug fix made it in... > > Wierd. > > > > --On Thursday, November 07, 2002 17:34:49 +0100 Olivier PRENANT > <[EMAIL PROTECTED]> wrote: > > > I see the latter in both b4 and b5! > > > > I've just relaunched my mirroring procedure and it did'nt pick another b4 > > or b5! > > > > What happens?? > > > > Regards, > > On Thu, 7 Nov 2002, Tom Lane wrote: > > > >> Date: Thu, 07 Nov 2002 11:26:42 -0500 > >> From: Tom Lane <[EMAIL PROTECTED]> > >> To: [EMAIL PROTECTED] > >> Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > >> [EMAIL PROTECTED], [EMAIL PROTECTED] > >> Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and > >> a > >> > >> Olivier PRENANT <[EMAIL PROTECTED]> writes: > >> > *WHAT??** > >> > this directory has hust been created by de-taring > >> > postgresql-7.3b5.tar.gz from my own mirror dated nov 6 20:04... > >> > >> Well, there's something darn weird here. Is > >> src/backend/utils/sort/tuplesort.c version 1.28 or 1.29? At line 1838, > >> do you see > >>inline int32 > >>ApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind kind, > >> or > >>static inline int32 > >>inlineApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind kind, > >> > >>regards, tom lane > >> > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > - > > - Make your life a dream, make your dream a reality. (St Exupery) > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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: [PORTS] [HACKERS] PostgreSQL supported platform report and a
I see the latter in both b4 and b5! I've just relaunched my mirroring procedure and it did'nt pick another b4 or b5! What happens?? Regards, On Thu, 7 Nov 2002, Tom Lane wrote: > Date: Thu, 07 Nov 2002 11:26:42 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > *WHAT??** > > this directory has hust been created by de-taring postgresql-7.3b5.tar.gz > > from my own mirror dated nov 6 20:04... > > Well, there's something darn weird here. Is > src/backend/utils/sort/tuplesort.c version 1.28 or 1.29? At line 1838, > do you see > inline int32 > ApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind kind, > or > static inline int32 > inlineApplySortFunction(FmgrInfo *sortFunction, SortFunctionKind kind, > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
*WHAT??** this directory has hust been created by de-taring postgresql-7.3b5.tar.gz from my own mirror dated nov 6 20:04... On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 10:07:37 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], Tom Lane <[EMAIL PROTECTED]> > Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > It looks like you do **NOT** have B4 or B5 > > LER > > > --On Thursday, November 07, 2002 17:00:21 +0100 Olivier PRENANT > <[EMAIL PROTECTED]> wrote: > > > On Thu, 7 Nov 2002, Tom Lane wrote: > > > >> Date: Thu, 07 Nov 2002 10:21:25 -0500 > >> From: Tom Lane <[EMAIL PROTECTED]> > >> To: [EMAIL PROTECTED] > >> Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > >> [EMAIL PROTECTED], [EMAIL PROTECTED] > >> Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and > >> a > >> > >> Olivier PRENANT <[EMAIL PROTECTED]> writes: > >> > Huh! I just tried to compile 7.3b5 without CFLAGS=-Xb, it still bugs > >> > the compiler... > >> > >> It won't get better if you don't show any details... > > Ok... (sorry) this is on UW 711 WITHOUT CFLAGS=-Xb: > > Script started on Thu Nov 7 16:57:05 2002 > > $ cd postgresql*5 > > $ make > > Using GNU make found at /usr/local/bin/gmake > > /usr/local/bin/gmake -C doc all > > gmake[1]: Entering directory `/home/postgres/postgresql-7.3b5/doc' > > gmake[1]: Nothing to be done for `all'. > > gmake[1]: Leaving directory `/home/postgres/postgresql-7.3b5/doc' > > /usr/local/bin/gmake -C src all > > gmake[1]: Entering directory `/home/postgres/postgresql-7.3b5/src' > > /usr/local/bin/gmake -C port all > > gmake[2]: Entering directory `/home/postgres/postgresql-7.3b5/src/port' > > gmake[2]: Nothing to be done for `all'. > > gmake[2]: Leaving directory `/home/postgres/postgresql-7.3b5/src/port' > > /usr/local/bin/gmake -C backend all > > gmake[2]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend' > > /usr/local/bin/gmake -C ../../src/port all > > gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/port' > > gmake[3]: Nothing to be done for `all'. > > gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/port' > > /usr/local/bin/gmake -C access all > > gmake[3]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access' /usr/local/bin/gmake > > -C common SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/common' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/common' > > /usr/local/bin/gmake -C gist SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/gist' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/gist' > > /usr/local/bin/gmake -C hash SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/hash' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/hash' > > /usr/local/bin/gmake -C heap SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/heap' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/heap' > > /usr/local/bin/gmake -C index SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/index' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/index' > > /usr/local/bin/gmake -C nbtree SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/nbtree' gmake[4]: > > `SUBSYS.o' is up to date. > > gmake[4]: Leaving directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/nbtree' > > /usr/local/bin/gmake -C rtree SUBSYS.o > > gmake[4]: Entering directory > > `/home/postgres/postgresql-7.3b5/src/backend/access/
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
On Thu, 7 Nov 2002, Tom Lane wrote: > Date: Thu, 07 Nov 2002 10:21:25 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>, > [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > Huh! I just tried to compile 7.3b5 without CFLAGS=-Xb, it still bugs the > > compiler... > > It won't get better if you don't show any details... Ok... (sorry) this is on UW 711 WITHOUT CFLAGS=-Xb: Script started on Thu Nov 7 16:57:05 2002 $ cd postgresql*5 $ make Using GNU make found at /usr/local/bin/gmake /usr/local/bin/gmake -C doc all gmake[1]: Entering directory `/home/postgres/postgresql-7.3b5/doc' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/postgres/postgresql-7.3b5/doc' /usr/local/bin/gmake -C src all gmake[1]: Entering directory `/home/postgres/postgresql-7.3b5/src' /usr/local/bin/gmake -C port all gmake[2]: Entering directory `/home/postgres/postgresql-7.3b5/src/port' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/home/postgres/postgresql-7.3b5/src/port' /usr/local/bin/gmake -C backend all gmake[2]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend' /usr/local/bin/gmake -C ../../src/port all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/port' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/port' /usr/local/bin/gmake -C access all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access' /usr/local/bin/gmake -C common SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/common' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/common' /usr/local/bin/gmake -C gist SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/gist' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/gist' /usr/local/bin/gmake -C hash SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/hash' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/hash' /usr/local/bin/gmake -C heap SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/heap' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/heap' /usr/local/bin/gmake -C index SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/index' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/index' /usr/local/bin/gmake -C nbtree SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/nbtree' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/nbtree' /usr/local/bin/gmake -C rtree SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/rtree' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/rtree' /usr/local/bin/gmake -C transam SUBSYS.o gmake[4]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/access/transam' gmake[4]: `SUBSYS.o' is up to date. gmake[4]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access/transam' gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/access' /usr/local/bin/gmake -C bootstrap all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/bootstrap' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/bootstrap' /usr/local/bin/gmake -C catalog all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/catalog' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/catalog' /usr/local/bin/gmake -C parser all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/parser' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/home/postgres/postgresql-7.3b5/src/backend/parser' /usr/local/bin/gmake -C commands all gmake[3]: Entering directory `/home/postgres/postgresql-7.3b5/src/backend/commands' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/h
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 08:41:58 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > > > >> Tom fixed that with a later tuplesort.c fix (per a discussion with the > >> Caldera/SCO > >> compiler guys). > > Huh! I just tried to compile 7.3b5 without CFLAGS=-Xb, it still bugs the > > compiler... > >> > Didn't for me :-( > > Wierd. BTW, this is on 7.1.1 not (yet) on 8.0.0 I'll let you know hopefully today. (How did you get 713 when it's due for december?) Can I have a copy? > > > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > --------- > > - Make your life a dream, make your dream a reality. (St Exupery) > > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
On Thu, 7 Nov 2002, Larry Rosenman wrote: > Date: Thu, 07 Nov 2002 06:41:02 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > > > > --On Thursday, November 07, 2002 13:32:18 +0100 Olivier PRENANT > <[EMAIL PROTECTED]> wrote: > > > That's true! > > > > But I had to export CFLAGS=-Xb to compile (this should be in port Makefile > > IMHO) > Tom fixed that with a later tuplesort.c fix (per a discussion with the > Caldera/SCO > compiler guys). Huh! I just tried to compile 7.3b5 without CFLAGS=-Xb, it still bugs the compiler... > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a
That's true! But I had to export CFLAGS=-Xb to compile (this should be in port Makefile IMHO) Also, I think the Setting of LD_LIBRARY_PATH could be a win to. Although I doubt anyone would run uw whith at least LD_LIBRARY_PATH=/lib:/usr/local/lib, setting LD_LIBRARY_PATH and includes in the port makefile could ease the configure process as readline is not found if you don't add --with-includes ans --with-libs on configure command. Reagrds On Wed, 6 Nov 2002, Larry Rosenman wrote: > Date: Wed, 06 Nov 2002 23:27:31 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform report and a > patch. > > We already have success messages from Olivier Prenant for 7.3B4 on 8.0.0, > and me for 7.1.3. > > I don't believe your changes are necessary. > > > > --On Wednesday, November 06, 2002 22:57:26 -0500 "Billy G. Allie" > <[EMAIL PROTECTED]> wrote: > > > I am including a set of 4 small patches that enable PostgreSQL 7.3b3 to > > build successfully on OpenUnix 8.0. These same patches should also work > > for UnixWare 7.x. I will confirm that tomorrow (Nov 7, 2002). > > > > Here is an explanation of the patches: > > > > 1. An update of the FAQ_SCO file. > > > > 2. This patch removes a static declaration of a in-line function in > >src/backend/utils/sort/tuplesort.c > > > > 3. This patch to src/makefiles/Makefile.unixware, together with the patch > > tosrc/Makefile.global.in allows any addition library search > > directories (addedwith the configure --with-libraries option) to be > > added to the rpath option sent to the linker. The use of a different > > variable to pass the addition search paths was necessary to avoid a > > circular reference to LDFLAGS. > > > > 4. This patch creates the variable (trpath) used by the patch to > >Makefile.unixware. This patch would also be for other platforms that > > would have to add the additional library search paths to the rpath > > linker option.See Makefile.unixware for an example of how to do this. > > > > After applying these patches, PostgreSQL successfully compiled on > > OpenUnix 8 and it passed all the regression tests. > > > > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.3b3 ok on unixware 71[12] here
Well, I think I just found it!! I adeed -Kpic in Dynaloader's Makefile. I haven't test plperl itself, but at least it compiles. Regards, On 30 Oct 2002, Larry Rosenman wrote: > Date: 30 Oct 2002 12:23:06 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [HACKERS] 7.3b3 ok on unixware 71[12] here > > On Wed, 2002-10-30 at 12:16, Olivier PRENANT wrote: > > On 30 Oct 2002, Larry Rosenman wrote: > > > > > Date: 30 Oct 2002 12:14:01 -0600 > > > From: Larry Rosenman <[EMAIL PROTECTED]> > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: [HACKERS] 7.3b3 ok on unixware 71[12] here > > > > > > > I've got it running with 5.8.0 of Perl. Is there anything holding you > > > back from updating to 5.8.0 of PERL? > > > > > Unfortunatly yes! Majordomo2 doesn't work quit well with 580. > > > > Is there anyway to ake 561 compile the way 580 does for dynaloader? > I had zero luck... Sorry. > > LER > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.3b3 ok on unixware 71[12] here
On 30 Oct 2002, Larry Rosenman wrote: > Date: 30 Oct 2002 12:14:01 -0600 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [HACKERS] 7.3b3 ok on unixware 71[12] here > > On Wed, 2002-10-30 at 12:08, Olivier PRENANT wrote: > > I'm glad to tell that I compiled and run regression tests ok on unixware > > 711 and 712 (Openunix 800) as well as on mac OS X 10.2.1 (execpt for > > float8) > > > > However, I'm still struggling to make plperl work on perl 561 and > > Unixware. > > > > I've scanned te Web and every thing without comming to a clue of what to > > do. It DID work on pg 723 though... > I've got it running with 5.8.0 of Perl. Is there anything holding you > back from updating to 5.8.0 of PERL? > Unfortunatly yes! Majordomo2 doesn't work quit well with 580. Is there anyway to ake 561 compile the way 580 does for dynaloader? Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] 7.3b3 ok on unixware 71[12] here
I'm glad to tell that I compiled and run regression tests ok on unixware 711 and 712 (Openunix 800) as well as on mac OS X 10.2.1 (execpt for float8) However, I'm still struggling to make plperl work on perl 561 and Unixware. I've scanned te Web and every thing without comming to a clue of what to do. It DID work on pg 723 though... Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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] Please help
Hi Tom, I can assure you that there are no problem anymore now that I have put the password. However the modification pg_hba.conf has been done a few days ago and never noticed the error until today where I had a *LOT* of visits to my site. So I still think it's a matter of bad connection delay. Connexion where comming very fast and postmaster did'nt release them fast enough. I now have this problem when I run vacuum analyze: Script started on Mon Oct 21 18:20:35 2002 ~ 18:20:35: psql pyrenet Password: Welcome to psql, 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 pyrenet=# VACUUM ANALYZE ; FATAL 2: could not open transaction-commit log directory (/usr/local/pgsql/data/pg_clog): Too many open files server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. Failed. !# \q ~ 18:21:21: psql pyrenet Password: Welcome to psql, 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 pyrenet=# VACUUM ANALYZE ; FATAL 2: could not open transaction-commit log directory (/usr/local/pgsql/data/pg_clog): Too many open files server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !# \q script done on Mon Oct 21 18:21:51 2002 What causes (FILES=64). Again, this is the very first time I have such problems on postgresql!! It works so well, it's the central point of my system!! On Mon, 21 Oct 2002, Tom Lane wrote: > Date: Mon, 21 Oct 2002 11:35:33 -0400 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Please help > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > It seems that connection from php pg_connect not supplying a password > > lives the process for a "certain ammount of time" running, then postmaster > > just hangs. > > That's hard to believe. In 7.2 or later, the backend should give up and > close the connection and exit if the client doesn't finish the > authentication handshake within 60 seconds. > > Can anyone else reproduce a problem with lack of a password on a PHP > connection? > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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] Please help
Thanks for your reply. Actually, I just found xhat happened 2 mn ago! Last week I changed my pg_hba.conf to require an md5 password for one specific database and updated all my script but ONE. It seems that connection from php pg_connect not supplying a password lives the process for a "certain ammount of time" running, then postmaster just hangs. Don't really know what happens here, but supplying a password on this script made the problem go away... (at least for now) Regards On Mon, 21 Oct 2002, Tom Lane wrote: > Date: Mon, 21 Oct 2002 11:02:43 -0400 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Please help > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > Without modifying anything, postgresql (since today) has a strange > > behavior: > > > All connections are rejected with No space left on device. > > Could you be out of swap space? > > I'd like to see the *exact* context in which you see this error message, > though. > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Please help
On Mon, 21 Oct 2002, Tom Lane wrote: > Date: Mon, 21 Oct 2002 12:52:10 -0400 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Please help > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > pyrenet=# VACUUM ANALYZE ; > > FATAL 2: could not open transaction-commit log directory >(/usr/local/pgsql/data/pg_clog): Too many open files > > Hmm. Do you have any idea what sysconf(_SC_OPEN_MAX) returns on your > platform? You could try reducing the max_files_per_process parameter. The point is, it occurs today for the very first time! Question: does (with 7.2) augmenting max_connection suffice, or do I have to recompile? That's the only thing that comes to my mind! I changed max_coneections (and related parameters) in postgresql.conf only... I say that, because I tried to change socket_directory in postgresql.conf and clients didn't work anymore > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] PL/Perl?
Well I spent half a day and half a night, pgsql compiles ok for me. However I'm still figuring why I have majodormo probs... So I went back for now. Regards On 5 Sep 2002, Larry Rosenman wrote: > Date: 05 Sep 2002 15:16:38 -0500 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: Tom Lane <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > Olivier PRENANT <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] PL/Perl? > > On Wed, 2002-09-04 at 19:41, Larry Rosenman wrote: > > On Wed, 2002-09-04 at 17:54, Tom Lane wrote: > > > Larry Rosenman <[EMAIL PROTECTED]> writes: > > > > I upgraded PostgreSQL to 7.2.1 from a 7.2beta (yeah, I know). One of my > > > > users requested plperl, so I got it to createlang, but it SIGSEGV's on > > > > any simple perl. > > > > > > I was seeing the same with perl 5.6.1 and PG 7.2.* on HPUX 10.20. > > > However, I have just verified that perl 5.8.0 works okay with PG CVS tip > > > (not much testing, but it handles a simple plperl function). Could you > > > see whether 5.8.0 plays any nicer on your setup? > > Need to check with my user, I'll let ya know. > > > Well, I tried to install 5.8.0 on my 8.0.1 (beta) system, and blew cc up > with an internal compiler error. I'll have to wait for Caldera to fix > that. Sorry. > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Bug in Makefile.shlib
Hi Tom, Thanks fr your reply.. Not sure I understood! I've tried your hack with no luck. Further more, README in perl/ext/Dynaloader says it has to be static to be effective. What concerns me more is that with same perl (5.6.1) it compiles ok with 722. Regards On Wed, 4 Sep 2002, Tom Lane wrote: > Date: Wed, 04 Sep 2002 17:14:13 -0400 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Larry Rosenman <[EMAIL PROTECTED]>, > pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Bug in Makefile.shlib > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > The problem is that at link time, ld complains about text segment beeing > > written to in Dynaloader. > > I agree this sounded stupid. But I can't think of something else. > > This is with perl-5.6.1 FWIW > > Ah. This is a bug in Perl's build process: even if you request a shared > library, it builds DynaLoader as static code. My own notes about > installing perl 5.6.1 on HPUX read: > > make > fix DynaLoader.o per below > make test > make install > > At least in 5.6.1, even with "build shared" request, DynaLoader.o is not > made with +z, which will cause plperl to fail. To fix, simply go into > perl-5.6.1/ext/DynaLoader, rm DynaLoader.o, and "make". I wonder why > toplevel makefile thinks it's okay to build DynaLoader static?? > > > I'm just now in the middle of installing Perl 5.8.0, and it seems that > the oversight has been fixed; DynaLoader is now built sharable: > > cc -c -Ae -D_HPUX_SOURCE -Wl,+vnocompatwarnings -DDEBUGGING -I/usr/local/include >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -DVERSION=\"1.04\" >-DXS_VERSION=\"1.04\" +Z "-I../.." -DPERL_CORE -DLIBC="/lib/libc.sl" DynaLoader.c > > There seem to be some other problems --- 7.2 plperl dumps core for me > even with the above fix. Still looking into that (I'm sorta hoping that > 5.8.0 will fix it, but won't know for a little while...) > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Bug in Makefile.shlib
Me again!! These are errors I get with orginal Makefile.shlib: Warning: No bytecode->native mapping for a bytecode Warning: JIT compiler failed for org/apache/crimson/parser/Parser2.maybeComment(Z)Z UX:ld: INFO: text relocations referenced from files: DynaLoader.a(DynaLoader.o) UX:ld: ERROR: relocations remain against non-writeable, allocatable section .text gmake[3]: *** [libplperl.so.0.0] Error 1 gmake[2]: *** [all] Error 2 gmake[1]: *** [all] Error 2 gmake: *** [all] Error 2 UX:make: ERROR: fatal error. Regards, On 4 Sep 2002, Larry Rosenman wrote: > Date: 04 Sep 2002 12:37:35 -0500 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: Tom Lane <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Bug in Makefile.shlib > > On Wed, 2002-09-04 at 12:28, Tom Lane wrote: > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > > I think I figured why I can't buil plperl on unixware 711/OpenUnix 800. > > > > > It seems Makefile.shlib has changed between 722 and 73 and -z text has > > > been added. > > > > Not hardly. The "-z text" option has been in there since at least 6.4. > > 6.4's Makefile.shlib has > > > > ifeq ($(PORTNAME), unixware) > > ... > > LDFLAGS_SL:= -G -z text > > ... > > endif > > > > which was cribbed from even older shlib support in other files. We used > > that up through 7.0 without any revisions. In 7.1 Makefile.shlib was > > revised pretty heavily; 7.1 has a unixware section that is identical to > > current sources, in particular > > > > LINK.shared += -Wl,-z,text -Wl,-h,$(soname) > > > > So I think this code is pretty well tested and removing the -z option > > is more likely to break things than fix them. > > > > What misbehavior are you seeing exactly? > see my post from ~2 weeks ago on -hackers with a 7.2.[12] problem. > > It flat doesn't work. > > I can dig the post up if you want. > > > > > > regards, tom lane > > > > ---(end of broadcast)--- > > TIP 5: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/users-lounge/docs/faq.html > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Bug in Makefile.shlib
Well, Tom and Larry, I've posted already on -hackers but my posts did'nt semm to get through! The problem is that at link time, ld complains about text segment beeing written to in Dynaloader. The only way was to remove -Wl,-z text. I agree this sounded stupid. But I can't think of something else. This is with perl-5.6.1 FWIW Regards On 4 Sep 2002, Larry Rosenman wrote: > Date: 04 Sep 2002 12:37:35 -0500 > From: Larry Rosenman <[EMAIL PROTECTED]> > To: Tom Lane <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Bug in Makefile.shlib > > On Wed, 2002-09-04 at 12:28, Tom Lane wrote: > > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > > I think I figured why I can't buil plperl on unixware 711/OpenUnix 800. > > > > > It seems Makefile.shlib has changed between 722 and 73 and -z text has > > > been added. > > > > Not hardly. The "-z text" option has been in there since at least 6.4. > > 6.4's Makefile.shlib has > > > > ifeq ($(PORTNAME), unixware) > > ... > > LDFLAGS_SL:= -G -z text > > ... > > endif > > > > which was cribbed from even older shlib support in other files. We used > > that up through 7.0 without any revisions. In 7.1 Makefile.shlib was > > revised pretty heavily; 7.1 has a unixware section that is identical to > > current sources, in particular > > > > LINK.shared += -Wl,-z,text -Wl,-h,$(soname) > > > > So I think this code is pretty well tested and removing the -z option > > is more likely to break things than fix them. > > > > What misbehavior are you seeing exactly? > see my post from ~2 weeks ago on -hackers with a 7.2.[12] problem. > > It flat doesn't work. > > I can dig the post up if you want. > > > > > > regards, tom lane > > > > ---(end of broadcast)--- > > TIP 5: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/users-lounge/docs/faq.html > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Bug in Makefile.shlib
Oops... This one should be all right!! Sorry Regards On Wed, 4 Sep 2002, Serguei Mokhov wrote: > Date: Wed, 4 Sep 2002 12:23:11 -0400 > From: Serguei Mokhov <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] Bug in Makefile.shlib > > - Original Message - > From: "Olivier PRENANT" <[EMAIL PROTECTED]> > Sent: September 04, 2002 12:18 PM > > > I think I figured why I can't buil plperl on unixware 711/OpenUnix 800. > > > > It seems Makefile.shlib has changed between 722 and 73 and -z text has > > been added. However with this on, it fails to build libperl.so > > > > Maybe I'm wrong, but could someone consider this patch. > > Your patch got it backwards :) > > -s > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) *** Makefile.shlib.orig mer sep 4 18:13:12 2002 --- Makefile.shlib mer sep 4 18:13:39 2002 *** *** 247,253 LINK.shared = $(CXX) -G endif endif ! LINK.shared += -Wl,-z,text -Wl,-h,$(soname) endif ifeq ($(PORTNAME), win) --- 247,253 LINK.shared = $(CXX) -G endif endif ! LINK.shared += -Wl,-h,$(soname) endif ifeq ($(PORTNAME), win) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Bug in Makefile.shlib
Hi, I think I figured why I can't buil plperl on unixware 711/OpenUnix 800. It seems Makefile.shlib has changed between 722 and 73 and -z text has been added. However with this on, it fails to build libperl.so Maybe I'm wrong, but could someone consider this patch. Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) *** Makefile.shlib mer sep 4 18:13:39 2002 --- Makefile.shlib.orig mer sep 4 18:13:12 2002 *** *** 247,253 LINK.shared = $(CXX) -G endif endif ! LINK.shared += -Wl,-h,$(soname) endif ifeq ($(PORTNAME), win) --- 247,253 LINK.shared = $(CXX) -G endif endif ! LINK.shared += -Wl,-z,text -Wl,-h,$(soname) endif ifeq ($(PORTNAME), win) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] can't post to the list
Sorry to bother, but it seems my last to messages (one to the news and one yesterday to the pghackers list) did'nt go through.. The problem related to difficulties with plperl and 7.3 on UW 711 Regards -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] WAL FILES
Hi Bruce, Thank you for your reply. It makes a lot of sense! However I don't really understand why we can't control the NUMBER of files. Are the 8 files I see a maximum usage when I reloaded the databases on the ne system or is it some sort of "plugged in value"? Thank you for your explanation. On Mon, 27 May 2002, Bruce Momjian wrote: > Date: Mon, 27 May 2002 17:17:58 -0400 (EDT) > From: Bruce Momjian <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS] WAL FILES > > Olivier PRENANT wrote: > > Hi every one. > > > > I just moved (at last!) to 7.2.1. Works like a charm... > > I'm suprised though by the number of WAL files. > > > > I have 8 files where postgresql.conf says WAL_FILES=4. > > > > What did I miss ? (I have no outstanding transaction) > > > > FWIW, t's on UW711. > > No, you are fine. The current GUC params are confusing. I did update > the documentation for 7.3, but I plan to reorganize those params to be > more meaningful. > > Actually, I have in TODO: > > Remove wal_files postgresql.conf option because WAL files are now > recycled > > because the param no longer controls what you think it controls. In 7.1 > WAL files where not recycled, so WAL_FILES was used to pre-allocate > files so there wasn't as much happening during checkpoint. Now, with > recycling, there is no need. > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] WAL FILES
Hi every one. I just moved (at last!) to 7.2.1. Works like a charm... I'm suprised though by the number of WAL files. I have 8 files where postgresql.conf says WAL_FILES=4. What did I miss ? (I have no outstanding transaction) FWIW, t's on UW711. Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] clarification of timestamp
High Thomas! Thanks for your reply. The columns in question are radius start and end of a connection of a custommer. Now, it's perfectly valid that start and stop cross a DST bondary in that case, the duration computed as (stop-start) maybe false. What do you think? I'm perfectly OK with leaving time sones on but the table is growing and I need dates indexes for my statistics. Hope I made my self clear (i.d pardon my english) Regards, On Mon, 29 Apr 2002, Thomas Lockhart wrote: > > My problem was that on my 7.1.3 db, I have timestamp columns with > > fonctinal indices as date(column). > > Thes indices (indexes) wont work anymore because they're not marked loosy. > > I've been told that I should go for timestamp without timezone instead, > > witch is okay because all timezones are the same. However, what happens > > with daylight saving calculations. Is it still take into account?? > > No, because there is no time zone to think about. What daylight savings > calculations would you need to consider? I'm a big believer in making > databases time zone aware, but if everything really is happening within > the same time zone then your application should probably not notice an > effect. > >- Thomas > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] clarification of timestamp
Hi all, I've already posted, a few weeks ago a concern about timestamp and indices. My problem was that on my 7.1.3 db, I have timestamp columns with fonctinal indices as date(column). Thes indices (indexes) wont work anymore because they're not marked loosy. I've been told that I should go for timestamp without timezone instead, witch is okay because all timezones are the same. However, what happens with daylight saving calculations. Is it still take into account?? Many thaks for that great product! Regards -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Bug or feature?
On Sat, 12 May 2001, Tom Lane wrote:
> Olivier PRENANT <[EMAIL PROTECTED]> writes:
> > Shoudn't postgres extend priviledges to the sequences generated by a
> > create table ???
>
> That's not clear. The sequence is an independent object. Had you
> explicitly done
>
> CREATE SEQUENCE myseq;
>
> CREATE TABLE mytab (f1 int default nextval('myseq'));
>
> would you expect that granting permissions on mytab automatically
> grants them on myseq as well? I think you might consider that
> surprising. But there isn't any difference between this and what
> CREATE TABLE does.
I'm aware of that.
>
> There have been suggestions in the past that SERIAL should be a "real
> data type" with the sequence object being hidden more effectively than
> it is now --- including auto-dropping it at table deletion, etc.
> If that were to happen then the permissions issue would probably go away
> too. It doesn't seem to be a very high priority for anyone, though.
>
IMHO, this would be "cleanner".
1) When you have lots of auto generated sequence, it becomes diffcult to
track the ones you have to drop if you drop tables.
2) This ACL problem could disapear if serial were a real type.
Anyway what I'm concerned with is that I had no problems until I dumped
from 7.0.3 and reloaded if 7.1.
Regards
> regards, tom lane
>
--
Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: [EMAIL PROTECTED]
--
Make your life a dream, make your dream a reality. (St Exupery)
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
Re: [HACKERS] Bug or feature?
Hi Tom, Thanks for your quick reply. However, I knew (and did that). My post were more ... philosophical: Shoudn't postgres extend priviledges to the sequences generated by a create table ??? Regards, On Fri, 11 May 2001, Tom Lane wrote: > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > I've just noticed that (after a upgrade from 7.0.3 to 7.1) the following > > did'nt work anymore: > > > create tabla a (n1 serial, n2 int); > > grant all on a to nobody; > > > > > > insert into a (n2) value (1); > > n1.nextval: you don't have permission to set sequence n1 > > > It worked on 7.0.3 > > You'll have to grant update rights on the sequence object to nobody ... > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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
[HACKERS] Bug or feature?
Hi, I've just noticed that (after a upgrade from 7.0.3 to 7.1) the following did'nt work anymore: create tabla a (n1 serial, n2 int); grant all on a to nobody; insert into a (n2) value (1); n1.nextval: you don't have permission to set sequence n1 It worked on 7.0.3 Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Re: Struggling with c functions
Many thanks to you!!!
It now works (did'nt realize that strings where not null
terminated) stupid me!!!
Regards,
On Sat, 28 Apr 2001, mlw wrote:
> You actually almost have it right.
>
> You are passing VARDATA(user) to crypt, this is wrong.
>
> You must do something like this:
>
> int ulen = VARSIZE(user)-VARHDRSZ;
> char utmp[ulen+]; // This works in newer GCC, cool.
> memcpy(utmp,VARDATA(user), len);
> utmp[ulen]=0;
> crypted=crypt(utmp,salt);
>
> Strings are not gurenteed to be NULL teminated.
>
>
> Olivier PRENANT wrote:
> >
> > Hi all,
> >
> > I'm rewriting my OLD crypt (Thanks to Henrique) C_fonction to version 0
> > forms :
> >
> > I have this C file compiled OK to a shared library:
> >
> > /*
> > *
> > * Henrique Pantarotto ([EMAIL PROTECTED])
> > * Funcao para encriptar senhas (Function to encrypt passwords)
> > * September 1999
> > *
> > * PS: Note that all crypted passwords are created with salt "HP" (my name
> > * initials..) You can change that, or if you know C, you can do in a way
> > * that it will pick two random characters (the way it should really be).
> > *
> > */
> >
> > #include
> > #include
> >
> > #include
> >
> > text *post_crypt(text *user)
> > {
> > text *password;
> > char * crypt();
> > long now=time((long *) 0);
> > int len;
> > char salt[7]="PY", *crypted;
> > /*strcpy(salt,l64a(now));
> >salt[3]='\0'; */
> > crypted=crypt(VARDATA(user),salt);
> > len=strlen(crypted);
> > password= palloc((int32) 13 + VARHDRSZ);
> > VARATT_SIZEP(password)= (int32) VARHDRSZ + 13;
> > memcpy(VARDATA(password),crypted,len);
> > return password;
> > }
> >
> > text *sql_crypt(text *user,text *salt)
> > {
> > text *password;
> > char * crypt(), *crypted;
> > int len;
> > char s[3];
> > strncpy(s,VARDATA(salt),2);
> > s[2]='\0';
> > crypted=crypt(VARDATA(user),s);
> > len=strlen(crypted);
> > password=palloc((int32) 13 + VARHDRSZ);
> > VARATT_SIZEP(password)=(int32) 13 + VARHDRSZ;
> > memcpy(VARDATA(password),crypted,len);
> > return password;
> > }
> >
> > /*
> > Compile using something like this:
> >
> > gcc -I/home/postgres/postgresql-6.5.1/src/include
>-I/home/postgres/postgresql-6.5.1/src/backend -O2 -Wall -Wmissing-prototypes -fpic
>-I/home/postgres/postgresql-6.5.1/src/include -c -o encrypt.o encrypt.c
> > gcc -shared -o encrypt.so encrypt.o
> >
> > And last, you create the trigger in PostgreSQL using this:
> >
> > create function encrypt(text)
> > returns text as '/usr/local/pgsql/lib/encrypt.so' language 'c';
> >
> > If everything is okay, you'll probably have: select encrypt('secret') working
> > and showing:
> >
> > encrypt
> >
> > HPK1Jt2NX21G.
> > (1 row)
> > */
> >
> > I have defined to SQL function:
> >
> > CREATE FUNCTION post_crypt(text) RETURNS text AS '/encrypt.so'
> > CREATE FUNCTION sql_cypt(text,text) RETURNS text AS '/encrypt.so';
> >
> > WHY on earth does
> >
> > SELECT post_crypt('test'),sql_crypt('test','PY')
> > NOT GIVE the same result???
> >
> > Please help,
> >
> > This is most urgent (My customer can't use this function anymore); it
> > worked OK with 7.0.3!!
> >
> > Regards,
> > --
> > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
> > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
> > 31190 AUTERIVE +33-6-07-63-80-64 (GSM)
> > FRANCE Email: [EMAIL PROTECTED]
> > --
> > Make your life a dream, make your dream a reality. (St Exupery)
> >
> > ---(end of broadcast)---
> > TIP 6: Have you searched our list archives?
> >
> > http://www.postgresql.org/search.mpl
>
>
--
Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: [EMAIL PROTECTED]
--
Make your life a dream, make your dream a reality. (St Exupery)
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] Struggling with c functions
Hi all,
I'm rewriting my OLD crypt (Thanks to Henrique) C_fonction to version 0
forms :
I have this C file compiled OK to a shared library:
/*
*
* Henrique Pantarotto ([EMAIL PROTECTED])
* Funcao para encriptar senhas (Function to encrypt passwords)
* September 1999
*
* PS: Note that all crypted passwords are created with salt "HP" (my name
* initials..) You can change that, or if you know C, you can do in a way
* that it will pick two random characters (the way it should really be).
*
*/
#include
#include
#include
text *post_crypt(text *user)
{
text *password;
char * crypt();
long now=time((long *) 0);
int len;
char salt[7]="PY", *crypted;
/*strcpy(salt,l64a(now));
salt[3]='\0'; */
crypted=crypt(VARDATA(user),salt);
len=strlen(crypted);
password= palloc((int32) 13 + VARHDRSZ);
VARATT_SIZEP(password)= (int32) VARHDRSZ + 13;
memcpy(VARDATA(password),crypted,len);
return password;
}
text *sql_crypt(text *user,text *salt)
{
text *password;
char * crypt(), *crypted;
int len;
char s[3];
strncpy(s,VARDATA(salt),2);
s[2]='\0';
crypted=crypt(VARDATA(user),s);
len=strlen(crypted);
password=palloc((int32) 13 + VARHDRSZ);
VARATT_SIZEP(password)=(int32) 13 + VARHDRSZ;
memcpy(VARDATA(password),crypted,len);
return password;
}
/*
Compile using something like this:
gcc -I/home/postgres/postgresql-6.5.1/src/include
-I/home/postgres/postgresql-6.5.1/src/backend -O2 -Wall -Wmissing-prototypes -fpic
-I/home/postgres/postgresql-6.5.1/src/include -c -o encrypt.o encrypt.c
gcc -shared -o encrypt.so encrypt.o
And last, you create the trigger in PostgreSQL using this:
create function encrypt(text)
returns text as '/usr/local/pgsql/lib/encrypt.so' language 'c';
If everything is okay, you'll probably have: select encrypt('secret') working
and showing:
encrypt
HPK1Jt2NX21G.
(1 row)
*/
I have defined to SQL function:
CREATE FUNCTION post_crypt(text) RETURNS text AS '/encrypt.so'
CREATE FUNCTION sql_cypt(text,text) RETURNS text AS '/encrypt.so';
WHY on earth does
SELECT post_crypt('test'),sql_crypt('test','PY')
NOT GIVE the same result???
Please help,
This is most urgent (My customer can't use this function anymore); it
worked OK with 7.0.3!!
Regards,
--
Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: [EMAIL PROTECTED]
--
Make your life a dream, make your dream a reality. (St Exupery)
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
[HACKERS] pg_dump problem
Hi all, I've read pg_dump threads with great interest as I plan to upgrade from 703 to 71 on next monday if 71 final is out. Although I did'nt have any of the ploblems listed in threads durin my tests from 7.0.3 to 7.1betas and 7.1RCs. I have noticed that pg_dump and pg_dumpall could'nt generate correctly CREATE FUNCTION when function has been created using the form CREATE FUNCTION foo(x) RETURNS type AS '/foo.so','foo2' LANGUAGE C; pg_dumps "forgets" the 'foo2' part: that being a pain in the a... when reloading... Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Contributions?
Hi Matthew, I would love to get this stuff... Could you send it to me or tell me where it is ? TIA On Tue, 6 Mar 2001, Matthew Hagerty wrote: > Greetings, > > I wrote a few simple programs to log Apache access_log entries to pg. If > this is something anyone would be interested in or if there is someplace I > can submit these to, please let me know. > > Thanks, > Matthew > > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery) ---(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] Re: int8 beta5 broken?
On Wed, 28 Feb 2001, Tom Lane wrote: > Olivier PRENANT <[EMAIL PROTECTED]> writes: > > Sorry to follow-up on my own post; int8 test passes if open-ssl is not > > used. > > That's difficult to believe, because int8.c doesn't include anything > that even knows SSL exists. Larry, can you confirm this behavior? Hi, I've been testing a little more further and found that (with-openssl) if initdb is done with LANG=C, int8 test succeeds if initdb is done with LANG=fr int8 test fails. I'll try nowwithout openssl and LANG=fr Regards > > regards, tom lane > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[HACKERS] Re: int8 beta5 broken?
Sorry to follow-up on my own post; int8 test passes if open-ssl is not
used.
weird!!
Regards,
On Wed, 28 Feb 2001, Olivier PRENANT wrote:
> Hi,
>
> Testing beta5 on unixware7 gives an error on int8 test while beta4 (I've
> just retested it) works ok regressions.diff follows:
>
> Also, compiling with openssl give a compile error on
> src/backend/libpq/crypt.c; this error CAN be avoided by commenting out the
> definition of des_encrypt in /ur/local/ssl/include/openssl/des.h
>
> I'm not sure this is good practice though.
>
> Anyway, even after that, there are linking errors on libecpg.so and perl
> because of a lack of -L/usr/local/ssl/lib
>
> Easyly avoid by setting ad hoc LD_LIBRARY_PATH.
>
> *** ./expected/int8.out Mon Jan 29 03:53:58 2001
> --- ./results/int8.outWed Feb 28 16:29:40 2001
> ***
> *** 5,111
> CREATE TABLE INT8_TBL(q1 int8, q2 int8);
> INSERT INTO INT8_TBL VALUES('123','456');
> INSERT INTO INT8_TBL VALUES('123','4567890123456789');
> INSERT INTO INT8_TBL VALUES('4567890123456789','123');
> INSERT INTO INT8_TBL VALUES('4567890123456789','4567890123456789');
> INSERT INTO INT8_TBL VALUES('4567890123456789','-4567890123456789');
> SELECT * FROM INT8_TBL;
> q1|q2
> ! --+---
> 123 | 456
> ! 123 | 4567890123456789
> ! 4567890123456789 | 123
> ! 4567890123456789 | 4567890123456789
> ! 4567890123456789 | -4567890123456789
> ! (5 rows)
>
> SELECT '' AS five, q1 AS plus, -q1 AS minus FROM INT8_TBL;
>five | plus | minus
> ! --+--+---
> | 123 | -123
> ! | 123 | -123
> ! | 4567890123456789 | -4567890123456789
> ! | 4567890123456789 | -4567890123456789
> ! | 4567890123456789 | -4567890123456789
> ! (5 rows)
>
> SELECT '' AS five, q1, q2, q1 + q2 AS plus FROM INT8_TBL;
>five |q1|q2 | plus
> ! --+--+---+--
> | 123 | 456 | 579
> ! | 123 | 4567890123456789 | 4567890123456912
> ! | 4567890123456789 | 123 | 4567890123456912
> ! | 4567890123456789 | 4567890123456789 | 9135780246913578
> ! | 4567890123456789 | -4567890123456789 |0
> ! (5 rows)
>
> SELECT '' AS five, q1, q2, q1 - q2 AS minus FROM INT8_TBL;
>five |q1|q2 | minus
> ! --+--+---+---
> | 123 | 456 | -333
> ! | 123 | 4567890123456789 | -456789012345
> ! | 4567890123456789 | 123 | 456789012345
> ! | 4567890123456789 | 4567890123456789 | 0
> ! | 4567890123456789 | -4567890123456789 | 9135780246913578
> ! (5 rows)
>
> SELECT '' AS three, q1, q2, q1 * q2 AS multiply FROM INT8_TBL
>WHERE q1 < 1000 or (q2 > 0 and q2 < 1000);
>three |q1|q2| multiply
> ! ---+--+--+
> | 123 | 456 | 56088
> !| 123 | 4567890123456789 | 561850485185185047
> !| 4567890123456789 | 123 | 561850485185185047
> ! (3 rows)
>
> SELECT '' AS five, q1, q2, q1 / q2 AS divide FROM INT8_TBL;
>five |q1|q2 | divide
> ! --+--+---+
> | 123 | 456 | 0
> ! | 123 | 4567890123456789 | 0
> ! | 4567890123456789 | 123 | 37137318076884
> ! | 4567890123456789 | 4567890123456789 | 1
> ! | 4567890123456789 | -4567890123456789 | -1
> ! (5 rows)
>
> SELECT '' AS five, q1, float8(q1) FROM INT8_TBL;
>five |q1|float8
> ! --+--+--
> | 123 | 123
> ! | 123 | 123
> ! | 4567890123456789 | 4.56789012345679e+15
> ! | 4567890123456789 | 4.56789012345679e+15
> ! | 45678901
[HACKERS] int8 beta5 broken?
SELECT q1 FROM int8_tbl UNION ALL (((SELECT q2 FROM int8_tbl EXCEPT SELECT q1 FROM int8_tbl))); q1 ! - 123 456 ! (2 rows) (((SELECT q1 FROM int8_tbl UNION ALL SELECT q2 FROM int8_tbl))) EXCEPT SELECT q1 FROM int8_tbl; q1 ! - 456 ! (1 row) -- -- Subqueries with ORDER BY & LIMIT clauses *** *** 399,408 SELECT q1,q2 FROM int8_tbl EXCEPT SELECT q2,q1 FROM int8_tbl ORDER BY q2,q1; q1|q2 ! --+--- ! 4567890123456789 | -4567890123456789 123 | 456 ! (2 rows) -- This should fail, because q2 isn't a name of an EXCEPT output column SELECT q1 FROM int8_tbl EXCEPT SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1; --- 367,375 SELECT q1,q2 FROM int8_tbl EXCEPT SELECT q2,q1 FROM int8_tbl ORDER BY q2,q1; q1 | q2 ! -+- 123 | 456 ! (1 row) -- This should fail, because q2 isn't a name of an EXCEPT output column SELECT q1 FROM int8_tbl EXCEPT SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1; *** *** 410,419 -- But this should work: SELECT q1 FROM int8_tbl EXCEPT (((SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1))); q1 ! -- 123 ! 4567890123456789 ! (2 rows) -- -- New syntaxes (7.1) permit new tests --- 377,385 -- But this should work: SELECT q1 FROM int8_tbl EXCEPT (((SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1))); q1 ! - 123 ! (1 row) -- -- New syntaxes (7.1) permit new tests *** *** 420,430 -- (select * from int8_tbl); q1|q2 ! --+--- 123 | 456 ! 123 | 4567890123456789 ! 4567890123456789 | 123 ! 4567890123456789 | 4567890123456789 ! 4567890123456789 | -4567890123456789 ! (5 rows) --- 386,392 -- (select * from int8_tbl); q1 | q2 ! -+- 123 | 456 ! (1 row) == -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
Re: [HACKERS] beta5 and unixware 711
On Tue, 27 Feb 2001, Larry Rosenman wrote: > * Olivier PRENANT <[EMAIL PROTECTED]> [010227 13:30]: > > Hi all, > > > > I've been trying to play with beta5 today on unixware 711. I have 2 > > problems: > > > > 1) enabling --with-tcl yields to link errors on bin/pgtclsh and > > interfaces/pl/tcl because Makefile insists on linking with libtcl7.6.0 > > instead on libtcl7.6 > With the Skunkware packages installed, it's fine here. You mean V802?? I had the same problems... > > > > 2) enabling --with-openssl causes a compilation error on > > src/backend/libpq/crypt.c because of multiply defined symbol des_encrypt > This is an OpenSSL error. We need to get THEIR attention > In the mean time, is there something I can do (apart from disbling ssl)? Regards, > LER > > > > > Regards, > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > ------ > > Make your life a dream, make your dream a reality. (St Exupery) > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[HACKERS] beta5 and unixware 711
Hi all, I've been trying to play with beta5 today on unixware 711. I have 2 problems: 1) enabling --with-tcl yields to link errors on bin/pgtclsh and interfaces/pl/tcl because Makefile insists on linking with libtcl7.6.0 instead on libtcl7.6 2) enabling --with-openssl causes a compilation error on src/backend/libpq/crypt.c because of multiply defined symbol des_encrypt Regards, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
Re: [HACKERS] BLOB HOWTO??
Bruce, Thanks for replying (I know you're a busy man :) Any chance to have it backported to 7.1 or maybe in contrib??? This is a feature w all gonna lack (with GiST...) Regards, On Mon, 29 Jan 2001, Bruce Momjian wrote: > > Hi Bruce, > > > > Any idea when it's due for?? > > I've been thining about writing a user function; But I'll get stuck with > > permission as a user function is running under the "postgres" or whatever > > user instead of the calling user. > > > > Also, what kind of binary interface are you thinking of?? > > Lack of large object support for new TOAST columns is going to be a big > 7.1 complaint. I was thinking of using the same functions as our large > object stuff, but remove the OID requirement. > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[SQL] BLOB HOWTO??
Hi, Beeing very impressed by TOAST, I wonder how I can insert BLOB from a flat file. It seems quite easy with php; But how can I do it from psql?? TIA -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
Re: [HACKERS] BLOB HOWTO??
Hi Bruce, Any idea when it's due for?? I've been thining about writing a user function; But I'll get stuck with permission as a user function is running under the "postgres" or whatever user instead of the calling user. Also, what kind of binary interface are you thinking of?? Regards, On Sun, 28 Jan 2001, Bruce Momjian wrote: > No way. We haven't written a binary interface to TOAST yet. > > > Hi, > > > > Beeing very impressed by TOAST, I wonder how I can insert BLOB from a flat > > file. > > > > It seems quite easy with php; But how can I do it from psql?? > > > > TIA > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > ---------- > > Make your life a dream, make your dream a reality. (St Exupery) > > > > > > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
Re: [HACKERS] psql -l bug
As I said previously.. I apologies, this was all my fault. Please discard... Oh my, When will we have an RC??? On Wed, 10 Jan 2001, Larry Rosenman wrote: > * Olivier PRENANT <[EMAIL PROTECTED]> [010110 12:47]: > > Hi, > > > > I just recompiled 7.1 beta from current CVS today. > > > > I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that > > psql -l shows 2 template0 and template1... > > > > Template0 and template1 belong to user postgres and to an other who has no > > priviledges and no db!!! > > > > What makes me think it's a psql bug is that select * from pg_databases > > show 1 template0 and 1 template1. > > > > For what it's worth, it on unixware 711. > > > > BTW, when is the release due for? I'm VERY impatient. This is the best > > I've seen. > I'm also on UW711, and do *NOT* see the bug: > > Password: > List of databases > Database | Owner | Encoding > ---+--+--- > ler | ler | SQL_ASCII > postgres | postgres | SQL_ASCII > template0 | postgres | SQL_ASCII > template1 | postgres | SQL_ASCII > (4 rows) > > > > > Regards,, > > > > -- > > Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) > > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > > FRANCE Email: [EMAIL PROTECTED] > > -- > > Make your life a dream, make your dream a reality. (St Exupery) > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[HACKERS] Re: psql -l bug
Sorry to folowup on my own post Problem solved: real and test db don't run on the same machine. On the test one, postgres had the same uid as pg_shadow.usesysid for the user... Sorry to have bothered you all. Reagrds On Wed, 10 Jan 2001, Olivier PRENANT wrote: > Hi, > > I just recompiled 7.1 beta from current CVS today. > > I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that > psql -l shows 2 template0 and template1... > > Template0 and template1 belong to user postgres and to an other who has no > priviledges and no db!!! > > What makes me think it's a psql bug is that select * from pg_databases > show 1 template0 and 1 template1. > > For what it's worth, it on unixware 711. > > BTW, when is the release due for? I'm VERY impatient. This is the best > I've seen. > > Regards,, > > -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[HACKERS] psql -l bug
Hi, I just recompiled 7.1 beta from current CVS today. I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that psql -l shows 2 template0 and template1... Template0 and template1 belong to user postgres and to an other who has no priviledges and no db!!! What makes me think it's a psql bug is that select * from pg_databases show 1 template0 and 1 template1. For what it's worth, it on unixware 711. BTW, when is the release due for? I'm VERY impatient. This is the best I've seen. Regards,, -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
[HACKERS] No digests today
Hi, Is there a problem? I haven't received anything today... -- Olivier PRENANT Tel:+33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: [EMAIL PROTECTED] -- Make your life a dream, make your dream a reality. (St Exupery)
