Re: [HACKERS] how to extend the catalog?
kevin [EMAIL PROTECTED] writes: I want to extend the catalog, What do you want to do *exactly*? is it enough: 1. add pg_xxx.h 2.modify pg_attribute.h, pg_class.h, pg_type.h, catname.h, indexing.h, indexing.c, Makefile You shouldn't need to touch pg_attribute.h, pg_class.h, pg_type.h, unless you are hacking one of the bootstrapped system tables or adding a new table that has to be known to the bootstrapper. 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
[HACKERS] Major change to CVS effective immediately ...
This will most likely screw some ppl up, and fix others ... CVSROOT has now moved to the new machine, finally ... and I've cleaned up pathing ... and CVS_RSH=ssh now works again too ... So, now CVSROOT is accessible as: :pserver:userid@cvs.postgresql.org:/cvsroot -or- :ext:userid@cvs.postgresql.org:/cvsroot - where CVS_RSH is set to ssh Now, I don't imagine it being *that* simple to move it over, so please let me know if anyone sees any errors on commits or stuff like that ... For those with already checked out repositories, from everything I've read, all you have to do is change the value of the CVS/Root file to point to the new Root ... This, I'm also figuring, is going to fix the email's going out as me for -committers ... anoncvs.postgresql.org is going to be out of sync until, most likely, tomorrow, for anyone trying to use that ... anoncvs is *no longer* available through the main cvs repository either ... ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Major change to CVS effective immediately ...
- Original Message - From: Marc G. Fournier [EMAIL PROTECTED] Sent: Sunday, September 16, 2001 1:05 PM Now, I don't imagine it being *that* simple to move it over, so please let me know if anyone sees any errors on commits or stuff like that ... CVSweb seems to be screwed up. It gives an error: 8 Error Error: $CVSROOT not found! The server on which the CVS tree lives is probably down. Please try again in a few minutes. 8 when I access it with my browser. Serguei ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Major change to CVS effective immediately ...
CVSWeb is going to be broken for a day or two, while Vince and I work out some issues as regards moving the main www site over to the same server ... but thanks for pointing it out, as I hadn't thought about it .. On Sun, 16 Sep 2001, Serguei Mokhov wrote: - Original Message - From: Marc G. Fournier [EMAIL PROTECTED] Sent: Sunday, September 16, 2001 1:05 PM Now, I don't imagine it being *that* simple to move it over, so please let me know if anyone sees any errors on commits or stuff like that ... CVSweb seems to be screwed up. It gives an error: 8 Error Error: $CVSROOT not found! The server on which the CVS tree lives is probably down. Please try again in a few minutes. 8 when I access it with my browser. Serguei ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Major change to CVS effective immediately ...
- Original Message - From: Marc G. Fournier [EMAIL PROTECTED] Sent: Sunday, September 16, 2001 1:37 PM CVSWeb is going to be broken for a day or two, while Vince and I work out some issues as regards moving the main www site over to the same server ... but thanks for pointing it out, as I hadn't thought about it .. It's just because the web interface is the only way for me for now I can access the CVS repository. Otherwise, I wouldn't have noticed the problem most likely... Serguei ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] Port of 7.1.2 to Lynx RT-OS
Greetings: I am (have attempted to) porting PostgreSQL 7.1.2 to Lynx RT OS (http://www.lynx.com). This OS does not support dynamic loading (on non-MIPS platforms). After successful build, I did a 'make check' and am getting the following errors. I would appreciate if anyone can point me toward the possible causes. Regards, -Chris History of changes: - renamed socket.h, pg_socket.h (to remove conflicts with socket.h which the compiler does not differentiate). - Changed 'yylval' in bootscanner.l to 'extern YYSTYPE yylval' to remove conflict with bootparse.c - and a few minor changes. The errors are: File: postmaster.log - /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: reaping dead processes... /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: ServerLoop: handling reading 5 /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: ServerLoop: handling reading 5 /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: ServerLoop: handling writing 5 /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: BackendStartup: pid 34 user postgres db template1 socket 5 /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster child[34]: starting with (postgres -d5 -v131072 -p template1 ) FindExec: found "/pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postgres" using argv[0] DEBUG: connection: host=127.0.0.1 user=postgres database=template1 DEBUG: InitPostgres DEBUG: _mdfd_blind_getseg: couldn't open /pg/postgresql-7.1.2/src/test/regress/./tmp_check/data/global/0: File or directory doesn't exist FATAL 1: cannot write block -1 of 0/0 blind: File or directory doesn't exist DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0) /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: reaping dead processes... /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: CleanupProc: pid 34 exited with status 0 Fast Shutdown request at Sun Sep 16 12:07:53 2001 DEBUG: shutting down NOTICE: Please reconnect to the database system and repeat your query.to terminate your database system connection and exit. /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: reaping dead processes... /pg/postgresql-7.1.2/src/test/regress/./tmp_check/install//pg/bin/postmaster: Shutdown proc 12 exited with status 256 -- 'make check' output ... $ tail log/make.check.out gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I. -I../../src/include -D__NO_INCLUDE_WARN__ -DHAVE_SYS_SHM_H -DREFINT_VERBOSE -c autoinc.c -o autoinc.o /bin/sh ./pg_regress --debug --temp-install --top-builddir=../../.. --schedule=./parallel_schedule --multibyte= == creating temporary installation== == initializing database system == == starting postmaster== running on port 65432 with pid 88 == creating database "regression" == psql: FATAL 1: cannot write block -1 of 0/0 blind: File or directory doesn't exist createdb: database creation failed pg_regress: createdb failed ---(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] Major change to CVS effective immediately ...
Marc G. Fournier writes: Now, I don't imagine it being *that* simple to move it over, so please let me know if anyone sees any errors on commits or stuff like that ... cvs commit ... cvs server: failed to create lock directory for \ `/cvsroot/pgsql/doc/src/sgml' (/cvsroot/pgsql/doc/src/sgml/#cvs.lock): \ Permission denied cvs server: lock failed - giving up cvs [server aborted]: lock failed - giving up For those with already checked out repositories, from everything I've read, all you have to do is change the value of the CVS/Root file to point to the new Root ... CVS/Repository as well. -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter ---(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] Major change to CVS effective immediately ...
On Sun, 16 Sep 2001, Peter Eisentraut wrote: Marc G. Fournier writes: Now, I don't imagine it being *that* simple to move it over, so please let me know if anyone sees any errors on commits or stuff like that ... cvs commit ... cvs server: failed to create lock directory for \ `/cvsroot/pgsql/doc/src/sgml' (/cvsroot/pgsql/doc/src/sgml/#cvs.lock): \ Permission denied cvs server: lock failed - giving up cvs [server aborted]: lock failed - giving up Okay, everything looks well to me on the server itself ... first stupid question, what is the IP of cvs.postgresql.org for you? it should be 85.28, but you might still have the old one cached ... ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Major change to CVS effective immediately ...
For those with already checked out repositories, from everything I've read, all you have to do is change the value of the CVS/Root file to point to the new Root ... CVS/Repository as well. Wouldn't you have to apply this change in *every* /CVS subdirectory of the tree? A fresh checkout seems easier. However, I find that the permissions problem stymies a checkout too... and yes, my DNS cache is up to date: $ nslookup cvs.postgresql.org Server: localhost Address: 127.0.0.1 Non-authoritative answer: Name:mail.postgresql.org Address: 216.126.85.28 Aliases: cvs.postgresql.org regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Major change to CVS effective immediately ...
Tom Lane writes:
Wouldn't you have to apply this change in *every* /CVS subdirectory of
the tree? A fresh checkout seems easier.
I just ran this on my tree:
find -name Root -exec perl -pi -e
's,:pserver:([a-z]+)\@postgresql.org:/home/projects/pgsql/cvsroot,:pserver:\1\@cvs.postgresql.org:/cvsroot,'
'{}' ';'
find -name Repository -exec perl -pi -e
's,/home/projects/pgsql/cvsroot/(.*),/cvsroot/\1,' '{}' ';'
and it looks like it didn't botch.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(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] factorial doc bug?
Thomas Lockhart [EMAIL PROTECTED] writes: Actually, it may be simply that we (now) implement factorial operators for int8, int4, and int2. Not sure what previous releases implemented, but perhaps it is just an issue of knowing which one should be used for the operation. If before we only had, say, int4, then the coersion code could easily assume that it was the correct coersion. I think this must be the correct explanation. Observe this experiment: regression=# create operator !! (procedure = int4fac, leftarg = int4); CREATE regression=# select 4.3 !!; ?column? -- 24 (1 row) regression=# create operator !! (procedure = int2fac, leftarg = int2); CREATE regression=# select 4.3 !!; ERROR: Unable to identify a postfix operator '!!' for type 'double precision' You may need to add parentheses or an explicit cast regression=# The int2 and int8 factorial operators were new in 7.0. The example in the docs is older --- its claim that there's only one factorial op in the catalogs is clearly out of date. So I'd say we should change the example. Have we got any other operators that only come in an int4 flavor, and are likely to stay that way? regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] factorial doc bug?
Thomas Lockhart [EMAIL PROTECTED] writes: ... Tom Lane is probably the person who made those changes, and we should have him in the discussion on whether the current behavior is appropriate. Keep in mind that he is a mathematician, and I'll guess that he won't have much patience with folks who expect a result for a factorial of a fractional number ;) Actually, I'm an engineer by training, not a mathematician --- either camp will tell you there's a big difference ;-) I have no objection to adding a float8 ! operator using the gamma-based definition, if someone felt like doing it. But even if we did, that would not fix the example in typeconv.sgml; indeed it would render the example completely wrong with respect to the point it was originally written to make. We need an operator that exists only for int4 to demonstrate implicit coercion. Unfortunately, I see no candidate for one in the current catalogs. Has anyone got another idea about how to replace this example with a correct one? 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
[HACKERS] 7.3
If removing artificial limitiations and improving 24/7 usability were considerations for 7.1 and 7.2, what will be the focus for 7.3? Personally, I would like to see the SQL features completed, ie: ADD PRIMARY KEY SET NULL / SET NOT NULL DROP COLUMN DROP PRIMARY KEY DROP UNIQUE DROP FOREIGN KEY I plan to work on all of these (except DROP COLUMN!), but my time is somewhat limited these days. What will everyone else be doing, particularly now that Great Bridge is gone? Chris ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] querying system catalogs to extract foreign keys
Or if you download WebPG (phpPgAdmin) it includes code for retrieving foreign keys. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Justin Clift Sent: Sunday, 16 September 2001 1:04 PM To: Rene Pijlman Cc: jiby george; [EMAIL PROTECTED] Subject: Re: [HACKERS] querying system catalogs to extract foreign keys Hi, In addition to this, Joel Burton's paper regarding Hacking the Referential Integrity tables gives very good insight into how to find out exactly what you're looking for, and the final example of SQL code at the end of the article will work as is : http://techdocs.postgresql.org/techdocs/hackingreferentialintegrity.php Modified code to show what you want : SELECT c.relname as Trigger Table, substr(f.proname, 9) as Trigger Function, t.tgconstrname as Constraint Name, c2.relname as Constraint Table, t.tgdeferrable as Deferrable?, t.tginitdeferred as Initially Deferred?, t.tgargs as Trigger Arguments FROM pg_trigger t, pg_class c, pg_class c2, pg_proc f WHERE t.tgrelid=c.oid AND t.tgconstrrelid=c2.oid AND tgfoid=f.oid AND t.tgenabled = 't' AND tgname ~ '^RI_' ORDER BY t.oid; Note the Trigger Arguments (bytea) column is where you look to find out the fields involved in the RI trigger. :-) Regards and best wishes, Justin Clift Rene Pijlman wrote: On 13 Sep 2001 22:56:16 -0700, you wrote: I tried to use the getImportedKeys and getExportedKeys of java.sql.DatabaseMetadata... But it didnt give any expected results... This is probably a limitation or bug in the JDBC driver. Please post details of your problem on [EMAIL PROTECTED] E.g. what results did you get, and what did you not get? So can anyone tell me how to query the system catalogs to extract this info?? The system catalogs are documented on http://www.postgresql.org/idocs/index.php?catalogs.html Regards, René Pijlman [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 -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 7.3
Christopher Kings-Lynne [EMAIL PROTECTED] writes: If removing artificial limitiations and improving 24/7 usability were considerations for 7.1 and 7.2, what will be the focus for 7.3? Whatever people want to work on. The above-stated descriptions of 7.1 and 7.2 work aren't bad, but they are after-the-fact summaries of what got done, not plans agreed on in advance. I learned awhile ago that trying to herd this bunch of cats is pointless ;-) FWIW, I think that schemas and tablespaces will be near the top of my own priority list. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] 7.2 RPMs
I just took a dreadful look at the RPMs. I've managed to build something
that resembles a 7.2 package, but there are a number of things that we
should talk about so this ends up being useful.
* The {pgaccess} parameter doesn't do anything AFAICT. PgAccess is
installed whenever Tk support is configured (which is correct, IMO).
Maybe this is just a legacy item?
* I removed the {plperl} parameter, because PL/Perl now builds by default
on Linux. Should plperl continue to stay its own package? I'd say yes,
because you don't need in on every client.
* Related to previous, the tcl package currently includes client and
server components. I'd say this is more useful as two separate packages.
* Similar issues with PL/Python
* Is libpgtcl.a supposed to be in the -libs package, while libpgtcl.so is
in -tcl? What about libpgtcl.h? Currently, the -devel package has an
implicit dependency on Tcl, which should probably not be there.
* How long do we want to keep the libpq.so.2.0 symlink?
* I fail to understand the motivation behind the way the -contrib package
is done. You seem to be installing the source code. I scrapped that and
installed the binaries the way it was designed to be.
* The -docs package is misleading. Maybe it should be called -docs-devel
or something. However, I'm having a hard time understanding how people
can make use of this.
* I request that rh-pgdump.sh and postgresql-dump be renamed to something
that conveys a semantic difference from pg_dump. Possibly, these files
should not be installed into /usr/bin if they're not general purpose.
* What about the JDBC driver? I think the driver should be compiled in
place by whatever JDK the build system provides.
* Start thinking about how to package National Language Support.
* Lot's of dependencies failing to be declared.
There are also a number of plain bug fixes that need to be integrated.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(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] 7.2 RPMs
Peter Eisentraut wrote: snip * What about the JDBC driver? I think the driver should be compiled in place by whatever JDK the build system provides. Don't know about the rest of this stuff, but I totally agree here. There should be a dependancy on Ant and some kind of JDK, and it should compile the driver specifically. This way the user I reckon the user is WAY more likely to have something which works well for them. Bumped into a problem with this just over a week ago. Regards and best wishes, Justin Clift snip -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter ---(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 -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] OSDN conference, vacation
Due to international instability, I have shortened my vacation and will remain in the US. Because of this, I _will_ be attending the upcoming OSDN database summit: http://www.osdn.com/conferences/osdb2/ I had previously reported I could not attend. Also, I will be around for more of the beta period. I should be out most of this week and at the OSDN summit the next week but should return late September to be involved in the beta process. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [GENERAL] Where do they find the time??? Great Bridge closed now!!!??
What a coincidence. I was about to say the exact opposite. Obviously, PostgreSQL isn't the one true database and everyone should Jump into MySQL. It is easier to type. I hope your post was meant as a joke because it was hilarious. These days MySQL is less of a database and more of an SQL interface to about 10 different database backend products... Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
