Re: [GENERAL] can we remove this guy from the list?
Can't help you, sorry :( Cannot unregister [EMAIL PROTECTED]: no matching addresses He probably is subscribed from some other address, and forwards it to that one ... I've even checked substrings of 'pdx.ne.jp' and 'ryo4893', just in case ... On Fri, 7 Apr 2006, Scott Marlowe wrote: Everytime I send an email to the pgsql-general list I get a failure message back saying this guy: [EMAIL PROTECTED] is over his local limit. Is it possible to remove him from the mailing list? Is it something I can do? I kinda doubt it, so that's why I'm asking here. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 1: 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: [GENERAL] can we remove this guy from the list?
Marc G. Fournier [EMAIL PROTECTED] writes: Can't help you, sorry :( Cannot unregister [EMAIL PROTECTED]: no matching addresses He probably is subscribed from some other address, and forwards it to that one ... I've even checked substrings of 'pdx.ne.jp' and 'ryo4893', just in case ... The bounces I've been getting (on more than one PG list) have tracebacks like this: Received: from hlmio02.pdx.ne.jp ([210.168.199.12]) by hl5emi1.wm.pdx.ne.jp id DAA25170 for [EMAIL PROTECTED]; Sat, 8 Apr 2006 03: 34: 30 +0900 (JST) Received: from mx1.rim.or.jp (hlegxh03.pdx.ne.jp [210.168.199.227]) by hlmio02.pdx.ne.jp (Postfix) with ESMTP id 65BC3AC5E2 for [EMAIL PROTECTED]; Sat, 8 Apr 2006 03: 34: 30 +0900 (JST) Received: from mx1.rim.or.jp ([202.247.191.99]) by hlegxh03.pdx.ne.jp with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sat, 8 Apr 2006 03: 34: 30 +0900 Received: from mx2.hub.org (mx2.hub.org [200.46.204.254]) by mx1.rim.or.jp (8.12.11/8.12.11) with ESMTP id k37IYO2U018177 for [EMAIL PROTECTED]; Sat, 8 Apr 2006 03: 34: 25 +0900 (JST) Received: from postgresql.org (postgresql.org [200.46.204.71]) by mx2.hub.org (Postfix) with ESMTP id 6F8A88B3C56; Fri, 7 Apr 2006 15: 34: 19 -0300 (ADT) X-Original-To: [EMAIL PROTECTED] See any entries for [EMAIL PROTECTED] ? regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Debian package for freeradius_postgresql module
On Fri, Apr 07, 2006 at 04:16:18PM -0700, Chris Travers wrote: By this interpretation, coding a connector against UNIX ODBC would be OK, but the user would be forbidden to use ODBC drivers that link against OpenSSL. I cannot therefore imagine a circumstance where the parent GPL application could be considered a dirivative work. Indeed indirect linking is a pretty common GPL dodge, given NVidia's approach to drivers. Please keep in mind that this has nothing to do with what users can or cannot do. The GPL is a *distribution* licence. It says, in no uncertain terms, that GPL programs must come with complete source of themselves and all dependancies under terms compatible with the GPL. The advertising clause in OpenSSL is not acceptable. Hence, Debian *as a distribution* cannot distribute precompiled binaries (freeradius) that would cause a GPL program to depend on code that cannot be distributed on compatable terms. People are ofcourse free to download the source themselves, they're just not allowed to distribute the resulting binaries. The issue is that installing freeradius-postgresql would install OpenSSL on the user's machine because libpq requires it. That's what's wrong with your example, the ODBC connector doesn't depend on OpenSSL so programs using it don't either. Did anyone notice the last few lines of the freeradius copyright file? It lists the modules in freeradius that directly or indirectly depend on OpenSSL and thus cannot be distributed *in precompiled form*. http://packages.debian.org/changelogs/pool/main/f/freeradius/freeradius_1.1.0-1.1/freeradius.copyright BTW, does this also mean that no GNU Readline is available in the Debian versions of psql? Or am I missing something? What has this to do with anything? We're talking about libpq depending on a GPL incompatable library, which GNU Readline obviously isn't. Have a nice day, -- Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/ Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. signature.asc Description: Digital signature
Re: [GENERAL] Postgres Library natively available for Mac OSX Intel?
Hello! Am 07.04.2006 um 13:50 schrieb User Roman: # [EMAIL PROTECTED] / 2006-03-31 10:05:06 +0200: I would like to know if somebody already has a Mac OSX Intel 10.4.5 pg-Library (for C, C++, Objective C) or knows how to compile it? What problems did you have building libpq? Note: I'm not an OSX user. I just wanted to know - I would like to have universal binaries of libpg and psql to deploy. Currently 8.1.3 compiles and runs just fine on OSX 10.4.6 + XCode 2.2.1, but generates binaries just for the current host architecture. Now when I add -arch i386 -arch ppc to CFLAGS and LDFLAGS for configure, then it compiles everything just fine, however at linking stage I get various problems for missing architecture files. Every generated .o file in the src build tree is actually an universal binary now, like for example ./src/timezone/SUBSYS.o: Mach header magic cputype cpusubtype filetype ncmds sizeofcmds flags 0xfeedface 7 3 1 4852 0x2000 Fat headers fat_magic 0xcafebabe nfat_arch 2 architecture 0 cputype 7 cpusubtype 3 offset 64 size 48100 align 2^5 (32) architecture 1 cputype 18 cpusubtype 0 offset 48192 size 69332 align 2^5 (32) ./src/timezone/zic.o: Mach header magic cputype cpusubtype filetype ncmds sizeofcmds flags 0xfeedface 7 3 1 3772 0x2000 So when make comes to the first linking this happens: gcc -no-cpp-precomp -arch i386 -arch ppc -Wall -Wmissing-prototypes - Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels - fno-strict-aliasing -L../../src/port -arch i386 -arch ppcaccess/ SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.o commands/ SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o main/SUBSYS.o nodes/SUBSYS.o optimizer/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o regex/SUBSYS.o rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o utils/ SUBSYS.o ../../src/timezone/SUBSYS.o ../../src/port/ libpgport_srv.a-lz -lreadline -lresolv -ldl -lm -o postgres /usr/bin/ld: for architecture ppc /usr/bin/ld: warning access/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning bootstrap/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning catalog/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning parser/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning commands/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning executor/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning lib/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning libpq/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning main/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning nodes/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning optimizer/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning port/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning postmaster/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning regex/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning rewrite/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning storage/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning tcop/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning utils/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld: warning ../../src/timezone/SUBSYS.o cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded) /usr/bin/ld:
[GENERAL] Load testing across 2 machines
Hi, I'm asking here in case this kind of thing has been done before, but I've not been able to find it.. We have two pg 8.1.3 servers, one live and one test. What I'd like to do is have something like pgpool to act as a connection broker, but instead of using pgpool's own replication where all queries are sent to both servers, and SELECTs are split between both servers, I'm aiming for this scenario: UPDATE/DELETE/INSERT go only to live, - Slony is replicating live to test. This permits test to go offline if necessary and easily 'catch up' later - much more convenient than pgpool's suggestion of 'stop both servers, then rsync the db files from master to slave'. SELECTS go to *both* live and test, but only the answers from live are sent back to clients - the answers from test are discarded... This would very gracefully allow the test machine to be monitored with real workload but without any danger of affecting the performance of the live system / returning bad data.. Has this been done already? Can it be done by extending pgpool or otherwise without requiring C coding skills? :) Cheers, Gavin. ---(end of broadcast)--- TIP 1: 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
[GENERAL] PostgreSQL (file based) database restore
I just did a file based database backup (stopped postmaster and zipped/copied all files under /usr/local/pgsql/data/* to a differnt location) How can I 'restore' the database and start using it? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] how to document database
Hi, I am not familiar with doxygen, so I can't give you any advice. To me postgresql_autodoc -d dbname works perfectly. I am useing version 1.25 of postgresql_autodoc. I recevice documentation of the sotred rocedures when I have comments on them. Then when postgresql_autodoc generate HTML documentation the comments are there. That's it. I am sorry if this doesn't help you much. Have a nice day, Kaloyan Iliev Ottavio Campana wrote: Kaloyan Iliev wrote: Hi, I'm using postgresql_autodoc. It is perfect for me. And if you have comments in the database the created document is like real documentation:-) I can't make it work. I'm running Debian etch, and I always get [EMAIL PROTECTED]:/tmp$ postgresql_autodoc -d tost Can't call method "finish" on an undefined value at /usr/bin/postgresql_autodoc line 1203. [EMAIL PROTECTED]:/tmp$ man postgresql_autodoc do you know what's wrong with it? And how do you document the stored procedures? can you have something similar to doxygen with postgresql_autodoc?
Re: [GENERAL] postmaster going down own its on
Title: RE: [GENERAL] postmaster going down own its on the scenario in which the above took place was somewhat like this we have a script to stop some of the processes running in the background. this script was run, and all the processes got stopped then another script will start these processes one after the other in background that script was run, and postmaster also got started. and then all of a sudden, it went down. thanks for the suggestions, i ll also look into the log essages and look for received fast shutdown message. but in case the postmaster received a fast shutdown signal, when the above mentioned script (to stop all processes in background). but again the script to start the processes including postmaster was run and at that time, postmaster did start, then how come it suddently went down. will provide u with more info on the same, thanks, regards surabhi -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED]] Sent: Fri 4/7/2006 8:51 PM To: Douglas McNaught Cc: Martijn van Oosterhout; Richard Huxton; surabhi.ahuja; pgsql-general@postgresql.org Subject: Re: [GENERAL] postmaster going down own its on *** Your mail has been scanned by InterScan VirusWall. ***-*** Douglas McNaught [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Could be. The actual standard use of SIGTERM is to kill processes belonging to your terminal process group when you log out. I thought that was SIGHUP? Doh. Not enough caffeine absorbed yet. As penance, here's a comment that I think is actually correct: sending SIGINT to the postmaster will make it turn around and send SIGTERM to all the backends. So there are two different explanations for the backends giving the administrator command error: either some outside force sent them SIGTERM directly, or some outside force sent the postmaster SIGINT. The SIGINT-the-postmaster theory is the more likely, I suspect, and that again could be associated with having carelessly left the postmaster attached to one's terminal. In any case, the first thing to do is look in the postmaster log and see if you see a message about received fast shutdown request, which would be proof one way or the other. regards, tom lane
Re: [GENERAL] PostgreSQL (file based) database restore
Bit Byter wrote: I just did a file based database backup (stopped postmaster and zipped/copied all files under /usr/local/pgsql/data/* to a differnt location) How can I 'restore' the database and start using it? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq stop the other postmaster then Unzip it then start the postmaster with the PGDATA pointed to the location of your files leonel ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] pgAdmin3 question
# [EMAIL PROTECTED] / 2006-04-07 14:31:04 -0700: A further question: we are using Debian system. So when we leave the 'Address' box blank (on the Add Server page of pgAdmin), according to the help file, it will go to use the default Postgresql socket on the local machine. We actually have a line as 'local all all ident sameuser' in the pg_hba.conf file. But when I tried, pgAdmin couldn't log the user in and shows Ident Authentication Failed. Then I modified the line pg_hba.conf file to 'local all all ident', and aaded a map line in the pg_ident.conf file to map the new user to user 'postgres'. Still not work. Did you instruct postmaster to reread the config files? http://www.postgresql.org/docs/8.1/static/client-authentication.html#AUTH-PG-HBA-CONF The pg_hba.conf file is read on start-up and when the main server process (postmaster) receives a SIGHUP signal. If you edit the file on an active system, you will need to signal the postmaster (using pg_ctl reload or kill -HUP) to make it re-read the file. http://www.postgresql.org/docs/8.1/static/auth-methods.html#AUTH-IDENT The pg_ident.conf file is read on start-up and when the main server process (postmaster) receives a SIGHUP signal. If you edit the file on an active system, you will need to signal the postmaster (using pg_ctl reload or kill -HUP) to make it re-read the file. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] postmaster going down own its on
On Sat, Apr 08, 2006 at 08:02:04PM +0530, surabhi.ahuja wrote: the scenario in which the above took place was somewhat like this we have a script to stop some of the processes running in the background. this script was run, and all the processes got stopped then another script will start these processes one after the other in background that script was run, and postmaster also got started. and then all of a sudden, it went down. So you stopped it and it stopped. You started it up again, and you say it stopped again. I'm sorry, you're going to have to post your logs before we can help you further. When you stop the postmaster you are sending a shutdown request, so it's not totally surprising that that message appears. Have a nice day, -- Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/ Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. signature.asc Description: Digital signature
Re: [GENERAL] pgAdmin3 question
-Original Message- From: lmyho [mailto:[EMAIL PROTECTED] Sent: 07 April 2006 22:31 To: Dave Page; pgsql-general@postgresql.org Subject: RE: [GENERAL] pgAdmin3 question --- Dave Page dpage@vale-housing.co.uk wrote: We have test database created in the initdb cluster, but on the Add Server page of pgAdmin3, the Maintenance DB dropdown box does not show this database. How can we make it to display this db in the dropdown box too? You can't without hacking the code. How to do this? Add the required lines to the dlgServer constructor in src/dlg/dlgServer.cpp, then recompile pgAdmin, eg. cbDatabase-Append(wxT(postgres)); cbDatabase-Append(wxT(template1)); // Add additional database options cbDatabase-Append(wxT(research)); cbDatabase-Append(wxT(sales)); Regards, Dave. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] Postgres Library natively available for Mac OSX Intel?
# [EMAIL PROTECTED] / 2006-04-08 14:04:28 +0200: Am 07.04.2006 um 13:50 schrieb User Roman: # [EMAIL PROTECTED] / 2006-03-31 10:05:06 +0200: I would like to know if somebody already has a Mac OSX Intel 10.4.5 pg-Library (for C, C++, Objective C) or knows how to compile it? What problems did you have building libpq? Note: I'm not an OSX user. I just wanted to know - I would like to have universal binaries of libpg and psql to deploy. Currently 8.1.3 compiles and runs just fine on OSX 10.4.6 + XCode 2.2.1, but generates binaries just for the current host architecture. Now when I add -arch i386 -arch ppc to CFLAGS and LDFLAGS for configure, then it compiles everything just fine, however at linking stage I get various problems for missing architecture files. Every generated .o file in the src build tree is actually an universal binary now, like for example sorry, this is way over my head. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] PostgreSQL (file based) database restore
Bit Byter wrote: I just did a file based database backup (stopped postmaster and zipped/copied all files under /usr/local/pgsql/data/* to a differnt location) How can I 'restore' the database and start using it? Assuming you are using linux/unix you can use pg_ctl (read the docs) to start the new database using the copy structure. There are a couple of assumptions that I am making for you: 1. You actually copied/archived the files correctly. 2. You have insured that the permissions are correct for the user that will be calling pg_ctl. 3. You didn't make the backups while the database was running. Lastly... don't do this. Use pg_dump/pg_restore. Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] LW Boston
Hello, As most of you probably know, we (PostgreSQL) were at LinuxWorld Boston this past week. The show although small, was very positive. We received alot of traffic and very specific pointed questions. This is the first show that I have been to where people were actually using PostgreSQL for their business. (OSCON was always about development). We had several people looking for DW and BI which Greenplum was a nice addition, plus a couple that were using OpenExchange. We were approached by several major corps including Unisys, Hitachi and AMD. Personally I also performed a talk at the Intel booth about PostgreSQL which seemed to go over well. The booth went off without a hitch and we had several community members there. Thanks everyone for helping us make the PostgreSQL booth the best OSS booth in the pavilion. Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] [pgsql-advocacy] LW Boston
Josh, Thanks everyone for helping us make the PostgreSQL booth the best OSS booth in the pavilion. Thank you for organizing it! -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] Debian package for freeradius_postgresql module
Tom Lane [EMAIL PROTECTED] writes: Stephen Frost [EMAIL PROTECTED] writes: Or are they selectively enforcing this policy against PG? It's enforced whenever we discover it, really... I am strongly tempted to pull Debian's chain by pointing out that libjpeg has an advertising clause (a much weaker one than openssl's, but nonetheless it wants you to acknowledge you used it) and demanding they rebuild all their GPL'd desktop apps without JPEG support forthwith. Except that's the GPL'd applications' licenses that are being violated, not yours. On the other hand have you checked any of the commercial products based on Debian to see if they're satisfying your advertising clause? I thought there was also a separate thread in this story in that the advertising clause was considered legally unenforceable and hence not really a problem for the GPL anyways. I'm not sure what happened to that story though and whether it was ever considered the case outside the US. I'm with Chris Travers on this: it's a highly questionable reading of the GPL, and I don't see why we should have to jump through extra hoops (like make-work porting efforts) to satisfy debian-legal. It's especially stupid because this is GPL code depending on BSD code, not vice versa. FWIW in any of the cases like where GPL'd application authors have actually pursued the issue the alleged infringers have always backed down after checking with lawyers. The classic example being the Objective-C frontend for gcc. In that case it was even *more* decoupled in that there wasn't even shared library linkage. It was purely a command-line and file format interface. Note that (as I understand it) nobody is saying Postgres is infringing on anything. Only that combining postgres with OpenSSL and Freeradius results in a combination of license restrictions that can't all be met at the same time. So the resulting binary package (which is useless without those other pieces of software) can't be legally distributed. -- greg ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] [ANN] PostgreSqlClient 2.0 Beta 1 released.
PostgreSqlClient ( old PgSqlClient ) 2.0 Beta 1 is available for download. It's the first version for ADO.NET 2.0 and Microsoft .NET 2.0, be aware that right now it doesn't provide integration with Visual Studio 2005. Download information can be found: http://sourceforge.net/project/showfiles.php?group_id=85397 Provider Home Page: http://pgsqlclient.sourceforge.net/ Best Regards Chris. ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[GENERAL] ANALYZE for a schema
I have multi company database where each company is stored in different schema. When I create incrementally new companis and add data to it ANALYZE command takes a lot of time: every time it analyzes the previous company data also. How to run ANALYZE command for a single schema ? Andrus. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] Cannot connect Postgresql 8.1 64 bit
I try to set FC3 X64 and postgresql 64 8.1 in my new server but I cannot connect it with pgadminIII. My pg_hba.conf is like below: # local is for Unix domain socket connections only local all all ident sameuser # IPv4 local connections: hostall all 127.0.0.1/32 trust sameuser hostall all 192.168.0.0/255.255.0.0 trust sameuser # IPv6 local connections: hostall all ::1/128 ident sameuser No fire wall was set and i cannot set it via webmin because of module configuration. What should I set in postgresql.conf to be able to connect to my postgres server? Thanks. Amrit Thailand ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] More PostgreSQL conversion fun
Hi all, I have a varchar field in a table which contains dates in -mm-dd format. The problem is that some have entered invalid dates like 1975-01-00 and I want to convert it to a date field to avoid this nonsense. Is there a way to test for failure of a type conversion and insert a NULL on failure? Thanks, Nick ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Cannot connect Postgresql 8.1 64 bit
Hi, On Sun, 2006-04-09 at 05:30 +0700, [EMAIL PROTECTED] wrote: I try to set FC3 X64 and postgresql 64 8.1 in my new server but I cannot connect it with pgadminIII. My pg_hba.conf is like below: # local is for Unix domain socket connections only local all all ident sameuser change ident sameuser to trust, reload PostgreSQL service... and read http://www.postgresql.org/docs/8.1/static/client-authentication.html about ident authentication. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Debian package for freeradius_postgresql module
As someone who licenses a lot of my code under the GPL, I feel inclined to correct you. Please note that IANAL. Martijn van Oosterhout wrote: On Fri, Apr 07, 2006 at 04:16:18PM -0700, Chris Travers wrote: By this interpretation, coding a connector against UNIX ODBC would be OK, but the user would be forbidden to use ODBC drivers that link against OpenSSL. I cannot therefore imagine a circumstance where the parent GPL application could be considered a dirivative work. Indeed indirect linking is a pretty common GPL dodge, given NVidia's approach to drivers. Please keep in mind that this has nothing to do with what users can or cannot do. The GPL is a *distribution* licence. No. It is a copyright license. It gives you the right to distribute the original work, create and distribute derivative works, etc. If it didn't give you the right to modify the code, then any code modifications would be subject to fair use law which doesn't exist in some places in the world (like Australia, for example). As for its scope, we may have to agree to disagree, or at least acknowledge that it may have different scopes in different places. Nowhere in the license does it say that you cannot link with other software. The FSF has been pretty clear that they consider linking to be analogous to derivation (and in many cases, it might be). Indeed the GPL v2 is no more clear on the matter of derivation than simply to refer to existing case law in whatever jurisdiction the coder happens to be in. For example, the FSF convinced Apple that they needed to comply the GPL when they were distributing binary objective C plugins to the GCC and then providing information for people to link them themselves. The result was that the GCC got open source Objective C support thanks to Apple. Do we know whether these plugins were really derivative works or not? Not really. But Apple chose not to fight it in court. However, there are clearly cases where linking would not be derivation in many jurisdictions. For example, if I create a perfectly standards-compliant ANSI C library, and I release it under the GPL, anyone can code ANSI C and use any number of C libraries in their compilation. The fact that one happens to compile it against my GPL work instead of any others would seem to be, while possibly an invitation to litigation, a pretty clear case of standard interfaces instead of derivation. At least in the US (IANAL, again), not everything can be copyrighted. I personally doubt that header files would be copyrightable for the purpose of making #include statements constitute derivation. Especially in the 9th Circuit, where you have the Gates Rubber test, I would think that the filtration step would remove any code copied by the compiler as a matter of making the program work with standard interfaces. THus with my ANSI C library, I don't think mere compilation against the GPL'd version would constitute derivation, but IANAL. It says, in no uncertain terms, that GPL programs must come with complete source of themselves and all dependancies under terms compatible with the GPL. The advertising clause in OpenSSL is not acceptable. No it doesn't. Otherwise you couldn't release a GPL'd program for Windows. It actually says that the derivative work as a whole must be released under the GPL. Whatever this means is up to the courts, unfortunately. The FSF has their opinion on their web site, but ultimately the only one who gets to interpret the license authoritatively is the court. Because nobody wants to fight there is no clear guidance. Best Wishes, Chris Travers Metatron Technology Consulting begin:vcard fn:Chris Travers n:Travers;Chris email;internet:[EMAIL PROTECTED] tel;work:509-888-0220 tel;cell:509-630-7794 x-mozilla-html:FALSE version:2.1 end:vcard ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] More PostgreSQL conversion fun
Nick Wiltshire wrote: Hi all, I have a varchar field in a table which contains dates in -mm-dd format. The problem is that some have entered invalid dates like 1975-01-00 and I want to convert it to a date field to avoid this nonsense. Is there a way to test for failure of a type conversion and insert a NULL on failure? Not the question you asked, but perhaps a suitable alternative: before attempting to convert, scan all the rows in the table looking for any contents of that column not fitting the format -mm-dd. Then you can either fix them or null them out. -- Guy Rouillier ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] Strange syntax for create/drop index
Hello, I have tried create/drop index in separate schema : example : create table : create table test.test(id integer not null,name varchar(30),constraint test_pkey primary key (id)) - ok create index test_name on test.test(name) - ok drop index test_name - not ok drop index test.test_name - ok create index test.test_name on test.test(name) - not ok 'drop index' request schema prefix, but 'create index' doesn't accept schema prefix this is strange for me Comments ? Best Peco ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] Debian package for freeradius_postgresql module
* Chris Travers ([EMAIL PROTECTED]) wrote: It says, in no uncertain terms, that GPL programs must come with complete source of themselves and all dependancies under terms compatible with the GPL. The advertising clause in OpenSSL is not acceptable. No it doesn't. Otherwise you couldn't release a GPL'd program for Windows. It actually says that the derivative work as a whole must be released under the GPL. Whatever this means is up to the courts, unfortunately. The FSF has their opinion on their web site, but ultimately the only one who gets to interpret the license authoritatively is the court. Because nobody wants to fight there is no clear guidance. The courts are pretty likely to strongly consider the copyright holder's opinion of the license when deciding how to interpret it. The fact that it hasn't been well-tested in court doesn't mean it's not something to be concerned with. Debian may be a little more cautious about this than some other Linux distributions but if anything in their case it's probably sensible since they don't have the funds to fight a court battle. Thanks, Stephen signature.asc Description: Digital signature
Re: [GENERAL] Strange syntax for create/drop index
On Apr 9, 2006, at 12:56 , Haris Peco wrote: 'drop index' request schema prefix, but 'create index' doesn't accept schema prefix Currently indexes must be in the same schema as the table they index, so no schema is accepted for CREATE INDEX. Indeed, the documentation for CREATE INDEX describes the name parameter so: http://www.postgresql.org/docs/current/interactive/sql- createindex.html#AEN42146 name The name of the index to be created. No schema name can be included here; the index is always created in the same schema as its parent table. However, you could have two or more indexes with the same name, but in different schemas, so you need to be able to schema-qualify an index when you drop it, so DROP INDEX accepts a schema-qualified name. Hope this helps. Michael Glaesemann grzm myrealbox com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] [pgsql-advocacy] LW Boston
Josh, On 4/8/06 10:59 AM, Joshua D. Drake [EMAIL PROTECTED] wrote: Thanks everyone for helping us make the PostgreSQL booth the best OSS booth in the pavilion. Thanks for hosting - Frank and Ayush had a great time and also said there was terrific interest there. It's an exciting time for Postgres! - Luke ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] Debian package for freeradius_postgresql module
Stephen Frost [EMAIL PROTECTED] writes: The courts are pretty likely to strongly consider the copyright holder's opinion of the license when deciding how to interpret it. It's worth pointing out here that 1. Debian is not the copyright holder. 2. The copyright holders, in this case the authors of freeradius, saw no problem with it. They'd hardly have written GPL-licensed software that depends on a BSD-licensed package if they did, because the strict intepretation says that their code is undistributable, and obviously they intend to distribute it. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Strange syntax for create/drop index
Michael, Thank you for answer, but you don't understand me I understood syntax and reason for this, but why postgreSQL doesn't accept this : create index test.test_name on test.test(name) schema prefix in 'create index' I know that it isn't necessary, because postgreSQL know that index is (must be) in table's schema, but this is natural for sql writers I expect that 'create ...' and 'drop ...' allow/request/don't accept schema prefix on same way Thanks Peco On Sunday 09 April 2006 02:08 am, Michael Glaesemann wrote: On Apr 9, 2006, at 12:56 , Haris Peco wrote: 'drop index' request schema prefix, but 'create index' doesn't accept schema prefix Currently indexes must be in the same schema as the table they index, so no schema is accepted for CREATE INDEX. Indeed, the documentation for CREATE INDEX describes the name parameter so: http://www.postgresql.org/docs/current/interactive/sql- createindex.html#AEN42146 name The name of the index to be created. No schema name can be included here; the index is always created in the same schema as its parent table. However, you could have two or more indexes with the same name, but in different schemas, so you need to be able to schema-qualify an index when you drop it, so DROP INDEX accepts a schema-qualified name. Hope this helps. Michael Glaesemann grzm myrealbox com ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Debian package for freeradius_postgresql module
* Tom Lane ([EMAIL PROTECTED]) wrote: Stephen Frost [EMAIL PROTECTED] writes: The courts are pretty likely to strongly consider the copyright holder's opinion of the license when deciding how to interpret it. It's worth pointing out here that 1. Debian is not the copyright holder. Not sure where you got the idea that I was suggesting they were, I certainly wasn't. 2. The copyright holders, in this case the authors of freeradius, saw no problem with it. They'd hardly have written GPL-licensed software that depends on a BSD-licensed package if they did, because the strict intepretation says that their code is undistributable, and obviously they intend to distribute it. GPL-licensed software depending on a BSD-licensed package *isn't* a problem. If we didn't link Postgres w/ OpenSSL this wouldn't be any issue at all. If the freeradius authors explicitly say they don't have a problem linking against a BSD-with-advertising-clause license (or even explicitly exempt OpenSSL) then it's all fine. Saying that because they wrote freeradius to support Postgres that they implicitly approve of the OpenSSL license is a more than a bit of a stretch. Thanks, Stephen signature.asc Description: Digital signature
Re: [GENERAL] More PostgreSQL conversion fun
I have a varchar field in a table which contains dates in -mm-dd format. The problem is that some have entered invalid dates like 1975-01-00 and I want to convert it to a date field to avoid this nonsense. Is there a way to test for failure of a type conversion and insert a NULL on failure? Hi, If you are using 8.0 or above you could write a plpgsql function and use a for select loop with a exception handler. In the loop try casting the column in question to date type and if a error is raised because of a invalid date set the column value to null. See this section in the docs: http://www.postgresql.org/docs/8.1/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING After you have cleaned up the bad dates, then change the column to a date type. Note: I have not tested this, but I think it should work :-) Later, -- Tony Caduto AM Software Design Home of PG Lightning Admin for Postgresql http://www.amsoftwaredesign.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Strange syntax for create/drop index
On Apr 9, 2006, at 13:33 , Haris Peco wrote: create index test.test_name on test.test(name) schema prefix in 'create index' I know that it isn't necessary, because postgreSQL know that index is (must be) in table's schema, but this is natural for sql writers Allowing a schema-qualified name for CREATE INDEX implies that there is a choice of schema you could choose. By disallowing the schema, it makes developers aware of the limitation of where the index can be created. If the schema was allowed, some people would infer that they can place the index in a schema other than the schema the table resides in, and they would get bitten when they try to do so. Michael Glaesemann grzm myrealbox com ---(end of broadcast)--- TIP 1: 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
