[HACKERS] Help compiling postgres
Hi all I'm trying to compile an old version of Postgres and suddenly I've got the folloging error message: make[2]: Cambiando a directorio `/home/jmilan/postgres-r/src/backend/port'gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o dynloader.o dynloader.cgcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o inet_aton.o inet_aton.cinet_aton.c:58: warning: no previous prototype for `inet_aton'gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o isinf.o isinf.cisinf.c:8:20: ieeefp.h: No existe el fichero o el directoriomake[2]: *** [isinf.o] Error 1make[2]: Saliendo directorio `/home/jmilan/postgres-r/src/backend/port'make[1]: *** [port.dir] Error 2make[1]: Saliendo directorio `/home/jmilan/postgres-r/src/backend'make: *** [all] Error 2 It is a modified version of Postgres to accept replication. Can anyone help me? Thanks to all J.M. Milan
[HACKERS] Fwd: [GENERAL] index not scanned
The topic below is quite common on the general list, people tend to ask without checking the documentation. I think most of those questions will disappear if the planner output is modified, so it is clear why a decision is made (maybe with an extra option). e.g. something like this if an index scan is possible but not used: EXPLAIN SELECT * FROM copy_of_forum_list_child WHERE f_id = 1 and father_name = 'top'; Seq Scan on copy_of_forum_list_child (cost=0.00..2.44 rows=1width=100, costs using index: 0.00...9.44 rows=... with=...) Any comments? Regards, Mario Weilguni -- Weitergeleitete Nachricht -- Subject: [GENERAL] index not scanned Date: Sun, 27 Oct 2002 12:46:39 +0200 From: Ben-Nes Michael [EMAIL PROTECTED] To: postgresql [EMAIL PROTECTED] Hi I add an Index to table that have only 30 rows. CREATE INDEX copy_of_forum_l_c_f_id_idx ON copy_of_forum_list_child ( f_id, father_name ); when i do: EXPLAIN SELECT * FROM copy_of_forum_list_child WHERE f_id = 1 and father_name = 'top'; its return: Seq Scan on copy_of_forum_list_child (cost=0.00..2.44 rows=1 width=100) why its not scanning the index ? does the planner knows that the table is small and it will take more time to check the index then stright check ? by the way, the table will get quite big in the future. Cheers ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) --- ---(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] beta3 packaged ...
Marc G. Fournier [EMAIL PROTECTED] writes: Please check it and confirm ... I believe everything, includin the docs, should be right on this ... if not, I'm going to repackage before announcing ... Code looks good from here, can't check the docs very easily over this dialup connection ... 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
Re: [HACKERS] Help compiling postgres
I'm trying to compile an old version of Postgres and suddenly I've got the folloging error message: This looks to be the working model of postgres-r. Did you get it via CVS or from the down load area? These questions should probably be asked on the pg-replication list instead of hackes. make[2]: Cambiando a directorio `/home/jmilan/postgres-r/src/backend/port' gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o dynloader.o dynloader.c gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o inet_aton.o inet_aton.c inet_aton.c:58: warning: no previous prototype for `inet_aton' gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -I.. -c -o isinf.o isinf.c isinf.c:8:20: ieeefp.h: No existe el fichero o el directorio make[2]: *** [isinf.o] Error 1 make[2]: Saliendo directorio `/home/jmilan/postgres-r/src/backend/port' make[1]: *** [port.dir] Error 2 make[1]: Saliendo directorio `/home/jmilan/postgres-r/src/backend' make: *** [all] Error 2 What OS are you using? I know the working model has worked on several versions of Red Hat, and Solaris, but I'm not sure it's been tested on many other OSs. Darren ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] beta3 packaged ...
On Sun, 27 Oct 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Please check it and confirm ... I believe everything, includin the docs, should be right on this ... if not, I'm going to repackage before announcing ... Code looks good from here, can't check the docs very easily over this dialup connection ... 'K, if I haven't heard anything negative by the time I'm finished the server upgrade this evening, I'll put out an announce ... Just need to confirm, beta3 *does* require an initdb from beta2, right? ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] 7.3 beta3 regression failure
I'm seeing this on my Linux box (kernel 2.4.18, glibc 2.2.4): *** ./expected/horology.out Thu Sep 19 06:35:25 2002 --- ./results/horology.out Mon Oct 28 13:42:39 2002 *** *** 537,549 SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' - interval '1 day')) as True; True -- ! t (1 row) SELECT (timestamp with time zone 'tomorrow' = (timestamp with time zone 'yesterday' + interval '2 days')) as True; True -- ! t (1 row) SELECT (timestamp with time zone 'tomorrow' 'now') as True; --- 537,549 SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' - interval '1 day')) as True; True -- ! f (1 row) SELECT (timestamp with time zone 'tomorrow' = (timestamp with time zone 'yesterday' + interval '2 days')) as True; True -- ! f (1 row) SELECT (timestamp with time zone 'tomorrow' 'now') as True; *** *** 790,796 + interval '02:01' AS time with time zone) AS time) AS 03:31:00; 03:31:00 -- ! 03:31:00 (1 row) SELECT CAST(cast(date 'today' + time with time zone '03:30' --- 790,796 + interval '02:01' AS time with time zone) AS time) AS 03:31:00; 03:31:00 -- ! 02:31:00 (1 row) SELECT CAST(cast(date 'today' + time with time zone '03:30' == ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 7.3 beta3 regression failure
I'm seeing this on my Linux box (kernel 2.4.18, glibc 2.2.4): *** ./expected/horology.out Thu Sep 19 06:35:25 2002 --- ./results/horology.outMon Oct 28 13:42:39 2002 [snip] Sorry, this must be due to summer time... -- Tatsuo Ishii ---(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] assignment type mismatch complaints
On Sat, 2002-10-26 at 18:34, Larry Rosenman wrote: On Sat, 2002-10-26 at 18:27, Tom Lane wrote: Larry Rosenman [EMAIL PROTECTED] writes: How concerned are we about assignment type mismatch warnings? They're probably all char versus unsigned char complaints? Probably. The first few I looked at are PG_GETARG_CSTRING to unsigned char assignments. (I can send the whole list to either you, Tom, or the list). There are a ton of them on compilers that care about it; most of 'em in the multibyte support. While it would be nice to clean up all that someday, I can't say that I think it's a really profitable use of time. Ok, I understand that. It seems that there are a bunch, but they are just warnings. One difficulty is that the obvious fix (add a bunch of casts) is probably a net degradation of the code. Explicit casts will hide mismatches that are a lot worse than char signedness, and so cluttering the code with them makes things more fragile IMHO. I think an acceptable fix would involve running around and changing datatype and function declarations; which is much more subtle and thought-requiring than throwing in a cast wherever the compiler burps. Understand, and I don't expect it to happen in a beta test :-). If anyone wants to look at these: ftp://ftp.lerctr.org/pub/pg-dev/gmake.out.txt Thanks, LER regards, tom lane -- 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 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- 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 ---(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] Time for RC1 soon?
Bruce Momjian [EMAIL PROTECTED] writes: Marc G. Fournier wrote: tom is away for the week, so I wouldn't see anything earlier hten the week following tha t... I talked to him about that and we both feel this week while he is away will be pretty quiet and the only major thing left is making sure our docs are ready and we have enough platform reports. Unless we see serious problem reports in the next week, I think RC1 on Friday is reasonable. (That assumes people get the platform tests done, of course.) 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
Re: [HACKERS] Request for supported platforms
On Saturday 26 October 2002 04:17, Bruce Momjian wrote: OK, Tom will be away next week, and Thomas will too. I can do it. Folks. start sending in those plaform reports, OS name and version number please. The current platform list is: http://developer.postgresql.org/docs/postgres/supported-platforms.html ianb uname -a IRIX64 Komma 6.5 07121148 IP27 ianb gcc -v Reading specs from /usr/local/lib/gcc-lib/mips-sgi-irix6.5/3.2/specs Configured with: ../configure --with-ld=/usr/bin/ld Thread model: single gcc version 3.2 Building 7.3b3; failed on four tests: abstime, tinterval, horology, join The first three are I presume due to the change to winter time (CET) earlier today (27.10), see http://www.postgresql.org/idocs/index.php?regress-evaluation.html#AEN18382 ; the join failure is a row ordering difference. Should it be of any use the regression.diffs file is here: http://home.akademie.de/~IBarwick/IRIX_65_regression.diffs Otherwise no apparent problems and the server started fine. Ian Barwick [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Request for supported platforms
Ports list updated: http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html --- Ian Barwick wrote: On Saturday 26 October 2002 04:17, Bruce Momjian wrote: OK, Tom will be away next week, and Thomas will too. I can do it. Folks. start sending in those plaform reports, OS name and version number please. The current platform list is: http://developer.postgresql.org/docs/postgres/supported-platforms.html ianb uname -a IRIX64 Komma 6.5 07121148 IP27 ianb gcc -v Reading specs from /usr/local/lib/gcc-lib/mips-sgi-irix6.5/3.2/specs Configured with: ../configure --with-ld=/usr/bin/ld Thread model: single gcc version 3.2 Building 7.3b3; failed on four tests: abstime, tinterval, horology, join The first three are I presume due to the change to winter time (CET) earlier today (27.10), see http://www.postgresql.org/idocs/index.php?regress-evaluation.html#AEN18382 ; the join failure is a row ordering difference. Should it be of any use the regression.diffs file is here: http://home.akademie.de/~IBarwick/IRIX_65_regression.diffs Otherwise no apparent problems and the server started fine. Ian Barwick [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [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 4: Don't 'kill -9' the postmaster
Re: [HACKERS] beta3 packaged ...
Marc G. Fournier wrote: On Sun, 27 Oct 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Please check it and confirm ... I believe everything, includin the docs, should be right on this ... if not, I'm going to repackage before announcing ... Code looks good from here, can't check the docs very easily over this dialup connection ... 'K, if I haven't heard anything negative by the time I'm finished the server upgrade this evening, I'll put out an announce ... Just need to confirm, beta3 *does* require an initdb from beta2, right? Yes. If we din't need an initdb, we may have just skipped beta3 and jumped right to RC1 next Friday. -- 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/users-lounge/docs/faq.html
Re: [HACKERS] beta3 packaged ...
On Sun, 27 Oct 2002, Bruce Momjian wrote: Marc G. Fournier wrote: On Sun, 27 Oct 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Please check it and confirm ... I believe everything, includin the docs, should be right on this ... if not, I'm going to repackage before announcing ... Code looks good from here, can't check the docs very easily over this dialup connection ... 'K, if I haven't heard anything negative by the time I'm finished the server upgrade this evening, I'll put out an announce ... Just need to confirm, beta3 *does* require an initdb from beta2, right? Yes. If we din't need an initdb, we may have just skipped beta3 and jumped right to RC1 next Friday. With the amount of chnages that went in between beta2 and no, there is no way that an RC1 would go out without a beta3 :) ---(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] Request for supported platforms
Bruce Momjian [EMAIL PROTECTED] writes: Ports list updated: Shouldn't the join regression test failure be fixed? Cheers, Neil -- Neil Conway [EMAIL PROTECTED] || PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Request for supported platforms
On an rh6.2, Linux gsX 2.4.19-pre6 #4 Thu Apr 11 07:17:39 CEST 2002 alpha unknown (ev56 ruffian) i get this failure. Should ./configure options gmake gmake check be the only things i need to do? == creating database regression == /home/mag/d/postgresql/postgresql-7.3b3/src/test/regress/./tmp_check/ins tall//usr/local/pgsql/bin/pg_encoding: error in loading shared libraries: /home/mag/d/postgresql/postgresql-7.3b3/src/test/regress/./tmp_check/ins tall//usr/local/pgsql/bin/pg_encoding: undefined symbol: pg_char_to_encoding createdb: SQL_ASCII is not a valid encoding name pg_regress: createdb failed gmake[2]: *** [check] Error 2 gmake[2]: Leaving directory `/home/mag/d/postgresql/postgresql-7.3b3/src/test/regress' gmake[1]: *** [check] Error 2 gmake[1]: Leaving directory `/home/mag/d/postgresql/postgresql-7.3b3/src/test' gmake: *** [check] Error 2 Magnus ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] Server downtime ...
Just a quick note that I'm going to be rebooting mars (the PostgreSQL.Org) server later on this evening to upgrade the OS ... downtime should be no more then 1 hour, unless something unforeseen happens ... ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] PostgreSQL v7.3beta3 Released
It has take just over a month to get to this point, but Beta3 is now ready and available for testing. Depending on the changes generated by this Beta, we are planning on release our first Release Candidate out within the week, with a full release shortly after. This Beta requires an initdb, so a dump/reload is required from previous betas. With this beta, we are looking to complete our list of supported platforms that is viewable at: http://developer.postgresql.org/docs/postgres/supported-platforms.html If you've been able to successful compile, and run, the regression tests on any of the platforms not listed as being supported for v7.3, please let us know by sending a note to [EMAIL PROTECTED] If you've been unable to do so, please send us in a report of the problem you hit, and, if its just the regression tests that failed, which tests failed, as well as a diff between your actual results and what is listed as the expected results. The list of changes between beta2 and beta3 is quite extensive, encompassing over 2000 lines in a ChangeLog format. A large portion of this is cosmetic changes (silencing compiler warnings) or documentation changes, but some of the more prominent changes consist of: - Function-call-style type coercions should be treated as explicit coercions, not implicit ones. - Perform transaction cleanup operations in a less ad-hoc, more principled order; in particular ensure that all shared resources are released before we release transaction locks. - Allow 8-byte off_t to properly pg_dump - Fix places that were using IsTransactionBlock() as an (inadequate) check that they'd get to commit immediately on finishing. - Fix ALTER TABLE ... ADD COLUMN for inheritance cases. - Make CREATE/ALTER/DROP USER/GROUP transaction-safe, or at least pretty nearly so, by postponing write of flat password file until transaction commit. - Fix potential problem with btbulkdelete deleting an indexscan's current item, if the page containing the current item is split while the indexscan is stopped and holds no read-lock on the page. - Rule rewriter was doing the wrong thing with conditional INSTEAD rules whose conditions might yield NULL. - Disallow aggregate functions in rule WHERE clauses. - Fix within-function memory leaks in the various PLs' interfaces to SPI_prepare - Fix case where a function in FROM returns a scalar type, but is referred to with whole-tuple syntax. - Invert logic in pg_exec_query_string() so that we set a snapshot for all utility statement types *except* a short list - Fix rewrite code so that rules are in fact executed in order by name, rather than being reordered according to INSTEAD attribute for implementation convenience. - Fix range-query estimation to not double-exclude NULLs - adds some missing functions for float8 math operations, specifically ceil(), floor(), and sign(). - And many many more ... Copies of beta3 are available on all the mirror sites, as well as at the main site under: ftp://ftp.postgresql.org/pub/beta A complete copy of the ChangeLog file is also available at the same location. Any bugs/problems with this release, please report it to [EMAIL PROTECTED] Marc G. Fournier Co-Ordinator PostgreSQL Global Development Group ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
