Re: [GENERAL] MediaWiki and Postgresql?
On 4/6/06, Jim Nasby <[EMAIL PROTECTED]> wrote: (...) > If I'm not confusing wiki's (and I'm offline now, so I can't check), > Mediawiki is pretty un-interested in supporting PostgreSQL (hard to > imagine why, given that some of their folks are paid by MySQL AB), so > a fork was created on pgFoundry. I believe it's called pgpedia. That'd be "wikipgedia": http://pgfoundry.org/projects/wikipedia/ Ian Barwick ---(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 Thu, Apr 06, 2006 at 02:39:44PM -0700, lmyho wrote: > > Sounds terribly unlikely, PostgreSQLs licence doesn't conflict with any > > use anywhere. Can you provide a reference? > > > > I wish things are not like this too! so I won't have to go through so much > trouble! > But that's what happened:-( > > This is the ref was given: > The old / original BSD license is not compatible. > http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses It's talking about BSD with advertising clause which doesn't apply to postgresql which has the modified BSD licence. I mean, Debian ships postgresql fine. Like I said, who said it isn't possible? Have a ncie day, -- Martijn van Oosterhout 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] MediaWiki and Postgresql?
On 4/4/06, Scott Marlowe <[EMAIL PROTECTED]> wrote: (...) > Given that this page: > > http://www.mediawiki.org/wiki/Help:%24wgDBtype > > says: > > Use ""mysql"" for working code and ""PostgreSQL"" for development/broken > code. The documentation in the MediaWiki wiki isn't always up to date, I suspect. > I'd guess that PostgreSQL support is not quite at the same level as > MySQL just yet. :) FWIW there's a file "includes/DatabasePostgreSQL.php" in the CVS head versions of MediaWiki which has at the top: /** * This is PostgreSQL database abstraction layer. * * As it includes more generic version for DB functions, * than MySQL ones, some of them should be moved to parent * Database class. * * STATUS: Working PG implementation of MediaWiki * TODO: Installer support * * @package MediaWiki */ (There's also "includes/DatabaseOracle.php" but it doesn't say anything about status). Ian Barwick ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Column descriptions - could they be propagated to new
On Thu, 6 Apr 2006, Jim Nasby wrote: I seem to recall some astronomer having created some custom types for storing astronomical data in PostgreSQL. Or perhaps he was using PostGIS. I know that other astronomers are using PostgreSQL/PostGIS so if you look around you might be able to save yourself quite a bit of work. Well I know about pgAstro and pgSphere (and helped a little in testing them) but maybe there are others. Will look, thanks. -- Clive Page Dept of Physics & Astronomy, University of Leicester, Leicester, LE1 7RH, U.K. ---(end of broadcast)--- TIP 6: explain analyze is your friend
[GENERAL] how to document database
I need to document the database I develop so that other people can easily understand how it works. I particularly want to document the stored procedures. By now I've used a javadoc style to document them. I can't use tools like doxygen on them but it is always better than nothing. I'd like to know if you're using some particular tool. Thanks -- Non c'è più forza nella normalità, c'è solo monotonia. signature.asc Description: OpenPGP digital signature
Re: [GENERAL] Debian package for freeradius_postgresql module
On Thu, Apr 06, 2006 at 02:40:03PM -0700, Tyler MacDonald wrote: > This looks like part of the debate: > > http://lists.debian.org/debian-legal/2002/11/msg00254.html > > I dont know if this applies to openssl though... Oh right, they're claiming that they can't distribute freeradius using postgresql because postgresql links to OpenSSL. freeradius is GPL which makes for an incompatabilty. Not something PostgreSQL is responsible for, given Debian could compile without SSL and the problem would be solved. About the only thing we could do is support GnuTLS, but that's about it. Have a nice day, -- Martijn van Oosterhout 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] how to document database
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? -- Non c'è più forza nella normalità, c'è solo monotonia. signature.asc Description: OpenPGP digital signature
Re: [GENERAL] FAQ 1.1
# [EMAIL PROTECTED] / 2006-04-06 12:03:18 -0400: > On Apr 3, 2006, at 11:23 PM, Chris Browne wrote: > >Yeah, someone at the office was asking me on the elevator about > >whether some Post-something was somehow up and coming. > > > >In retrospect, I think he was trying to pronounce Postgre, and arrived > >at something I had never heard before... > > And it doesn't help when "post-something" could also mean a very > popular MTA... Looks like a missed opportunity for a April 1st announcement of disambiguating the two by renaming "postgres" to "pregross". :) -- 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] Postgres Library natively available for Mac OSX Intel?
# [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. -- 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 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: %Re: [GENERAL] % tsearch gendict
I see there are some changes in tsearch from postgresql 7.4.3 to postgresql 8.1.3 version, you add some new functions i think and change the tsearch.sql template right? I don't remember what exactly, but why do you ask? Different version on Gentroo and Sun? There is a lot tsearch2 improvements in 8.0. Tsearch 2 is now working on solaris Good -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(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] Use functions in Pl/Perl language
# [EMAIL PROTECTED] / 2006-03-29 17:17:48 -0800: > Hello, > > I would like to create a function that lets me to search in a table > rows according differents parameters. > I looked in the documentation of postgresql 8.1 about Pl/Perl > procedures but I didn't found how to cross each row of a table with > Pl/Perl. > > Someone would have an example of that with Pl/Perl language ? see the lotsa_md5() example at http://www.postgresql.org/docs/8.1/static/plperl-database.html -- 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 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] postmaster going down own its on
hi, is it possible for postmaster to go doen on its own? all what the logs say is FATAL: terminating connection dur to administrator's command. thanks, regards Surabhi
Re: [GENERAL] FAQ 1.1
On Fri, Apr 07, 2006 at 10:26:32AM +, User Roman wrote: > Looks like a missed opportunity for a April 1st announcement > of disambiguating the two by renaming "postgres" to "pregross". :) Not exactly that change, but http://archives.postgresql.org/pgsql-hackers/2005-04/msg00023.php -- Michael Fuhr ---(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] postmaster going down own its on
It's not normal. What's the installation? OS, applications connecting to the server, etc. On Apr 7, 2006, at 8:20 AM, surabhi.ahuja wrote:hi, is it possible for postmaster to go doen on its own? all what the logs say is FATAL: terminating connection dur to administrator's command. thanks, regards Surabhi
RES: [GENERAL] FAQ 1.1
How much bullshit! is there no more nothing to do? >-Mensagem original- >De: Michael Fuhr [mailto:[EMAIL PROTECTED] >Enviada em: sexta-feira, 7 de abril de 2006 09:22 >Para: Jim Nasby; Chris Browne; pgsql-general@postgresql.org >Assunto: Re: [GENERAL] FAQ 1.1 > > >On Fri, Apr 07, 2006 at 10:26:32AM +, User Roman wrote: >> Looks like a missed opportunity for a April 1st announcement >> of disambiguating the two by renaming "postgres" to >"pregross". :) > >Not exactly that change, but > >http://archives.postgresql.org/pgsql-hackers/2005-04/msg00023.php > >-- >Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] postmaster going down own its on
surabhi.ahuja wrote: hi, is it possible for postmaster to go doen on its own? all what the logs say is FATAL: terminating connection dur to administrator's command. Someone or something is issuing a kill command. It couldn't be the infamous Linux out-of-memory handler, could it? Check your system logs for details. -- Richard Huxton Archonet Ltd ---(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
ENC: [GENERAL] FAQ 1.1
is there no more nothing to do? >-Mensagem original- >De: Michael Fuhr [mailto:[EMAIL PROTECTED] >Enviada em: sexta-feira, 7 de abril de 2006 09:22 >Para: Jim Nasby; Chris Browne; pgsql-general@postgresql.org >Assunto: Re: [GENERAL] FAQ 1.1 > > >On Fri, Apr 07, 2006 at 10:26:32AM +, User Roman wrote: >> Looks like a missed opportunity for a April 1st announcement >> of disambiguating the two by renaming "postgres" to >"pregross". :) > >Not exactly that change, but > >http://archives.postgresql.org/pgsql-hackers/2005-04/msg00023.php > >-- >Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org ---(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] help needed (which group do I post these questions to?)
I am getting a little desperate as I have not got any replies yet. I am wondering if this is the correct group for my questions. If not, please point me to the appropriate group. My questions revolve around libpq. 1). Does anyone know how to execute a stored procedure (i.e. PL/PGSQL function), using libpq, and passing it parameters?. An example will be superb, as I have not managed to find one that does this after about a week of Googling. 2). I have written some C extensions to the server (user defined functions), these work fine on Limux. I now wnat to eb able to recompile my code to a shared library so that I can use my UDF in my Windows (PG 8.1) installation. I cannot seem to find any examples that show how this can be done. Do I need the cygwin tools or can I build the dll using VC++? I look forward to any answers (or possibly, a redirection to the appropriate group) MTIA ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] could not create shared memory segment in Windows XP
Have you got Cygwin installed? I had similar problems due to Cygwin being eariler in my PATH than Pg. Regards, Ben "Andrus" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'm unable to create database cluster in Windows 2000 server. > > initdb returns error > > FATAL: could not create shared memory segment: No such file or directory > > any idea how to create cluster in Windows 2000 ? > > > Task MAnager shows physical memory: > > Total: 392664 > Available: 81860 > System Cache: 157xxx > > > If available physical memory is too low, how to increate it (decrease > system cache) ? > > Andrus. > > > C:\pgsql>bin\initdb -E=UTF8 -d -D data > Running in debug mode. > VERSION=8.1.3 > PGDATA=data > share_path=C:/pgsql/share > PGPATH=C:/pgsql/bin > POSTGRES_SUPERUSERNAME=postgres > POSTGRES_BKI=C:/pgsql/share/postgres.bki > POSTGRES_DESCR=C:/pgsql/share/postgres.description > POSTGRESQL_CONF_SAMPLE=C:/pgsql/share/postgresql.conf.sample > PG_HBA_SAMPLE=C:/pgsql/share/pg_hba.conf.sample > PG_IDENT_SAMPLE=C:/pgsql/share/pg_ident.conf.sample > The files belonging to this database system will be owned by user > "postgres". > This user must also own the server process. > > The database cluster will be initialized with locale > Estonian_Estonia.1257. > > creating directory data ... ok > creating directory data/global ... ok > creating directory data/pg_xlog ... ok > creating directory data/pg_xlog/archive_status ... ok > creating directory data/pg_clog ... ok > creating directory data/pg_subtrans ... ok > creating directory data/pg_twophase ... ok > creating directory data/pg_multixact/members ... ok > creating directory data/pg_multixact/offsets ... ok > creating directory data/base ... ok > creating directory data/base/1 ... ok > creating directory data/pg_tblspc ... ok > selecting default max_connections ... 10 > selecting default shared_buffers ... 50 > creating configuration files ... ok > creating template1 database in data/base/1 ... DEBUG: TZ > "Europe/Helsinki" > matc > hes Windows timezone "FLE Daylight Time" > DEBUG: invoking IpcMemoryCreate(size=1327104) > DEBUG: mapped win32 error code 161 to 2 > FATAL: could not create shared memory segment: No such file or directory > DETAIL: Failed system call was shmget(key=1, size=1327104, 03600). > DEBUG: proc_exit(1) > DEBUG: shmem_exit(1) > DEBUG: exit(1) > child process was terminated by signal 1 > initdb: removing data directory "data" > > > ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] help needed (which group do I post these questions to?)
On Thu, Apr 06, 2006 at 05:39:00PM -0700, Bit Byter wrote: > 1). Does anyone know how to execute a stored procedure (i.e. PL/PGSQL > function), using libpq, and passing it parameters?. An example will be > superb, as I have not managed to find one that does this after about a > week of Googling. SELECT myfunction(arg1, arg2); -- for simple function SELECT * FROM myfunction(arg1, arg2); -- for set returning functions > 2). I have written some C extensions to the server (user defined > functions), these work fine on Limux. I now wnat to eb able to > recompile my code to a shared library so that I can use my UDF in my > Windows (PG 8.1) installation. I cannot seem to find any examples that > show how this can be done. Do I need the cygwin tools or can I build > the dll using VC++? You need to use the exact same setup as used to build the server. I'm unsure how this is done in Windows, there was some discussion about compatability, but the easiest is to grab the source and compile both the server and extensions within that. Have a nice day, -- Martijn van Oosterhout 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] case insensitive match in unicode
On Thu, Apr 06, 2006 at 11:12:26PM +0200, SunWuKung wrote: > > There is also a locale-independant case-mapping module there plus > > various locale specific ones also. > > > > http://icu.sourceforge.net/userguide/Transform.html > > http://icu.sourceforge.net/userguide/caseMappings.html > > http://icu.sourceforge.net/userguide/normalization.html > > > > Have a nice day, > > > Thanks, I looked at this and it looks like something that would indeed > solve the problem. > However I was so far unable to figure out how could I use this from > within Postgres. If you have experience with it could you give me an > example? There are some unofficial ICU patches but I doubt they're still up-to-date. I don't personally use it though maybe someone else here does... Have a nice day, -- Martijn van Oosterhout 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] postmaster going down own its on
Richard Huxton writes: > surabhi.ahuja wrote: >> hi, is it possible for postmaster to go doen on its own? >> all what the logs say is FATAL: terminating connection dur to >> administrator's command. > > Someone or something is issuing a kill command. It couldn't be the > infamous Linux out-of-memory handler, could it? Check your system logs > for details. I'm not sure it's that--the OOM killer uses SIGKILL which would take down the server before it could write that log entry. -Doug ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: RES: [GENERAL] FAQ 1.1
Renato Cramer <[EMAIL PROTECTED]> writes: > How much bullshit! > > is there no more nothing to do? Take a close look at the message date. :) -Doug ---(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] postmaster going down own its on
Douglas McNaught wrote: Richard Huxton writes: surabhi.ahuja wrote: hi, is it possible for postmaster to go doen on its own? all what the logs say is FATAL: terminating connection dur to administrator's command. Someone or something is issuing a kill command. It couldn't be the infamous Linux out-of-memory handler, could it? Check your system logs for details. I'm not sure it's that--the OOM killer uses SIGKILL which would take down the server before it could write that log entry. Hmm... (tests it) you're right. What would be sending SIGTERM to a backend? -- Richard Huxton Archonet Ltd ---(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: %Re: [GENERAL] % tsearch gendict
Teodor Sigaev wrote: I see there are some changes in tsearch from postgresql 7.4.3 to postgresql 8.1.3 version, you add some new functions i think and change the tsearch.sql template right? I don't remember what exactly, but why do you ask? Different version on Gentroo and Sun? There is a lot tsearch2 improvements in 8.0. Tsearch 2 is now working on solaris Good Sorry for the missunderstanding, I was working with a postgresql 7.4.3 on Gentoo 2004, and now on Solaris 10 and postgresql 8.1.3 , so since 7.4.3 I suppose tsearch has improvements as you say. Thanks Teodor ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] postmaster going down own its on
On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote: > >I'm not sure it's that--the OOM killer uses SIGKILL which would take > >down the server before it could write that log entry. > > Hmm... (tests it) you're right. What would be sending SIGTERM to a backend? The only other thing I've ever heard of is some systems do a sigterm when you pass a quota limit? Not sure though, -- Martijn van Oosterhout 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] case insensitive match in unicode
On 4/6/06, SunWuKung <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>, kleptog@svana.org says...
> > On Mon, Mar 27, 2006 at 12:45:05PM +0200, SunWuKung wrote:
> > > This sounds like a very interesting concept.
> > > It wouldn't be 'case insensitive' just insensitive.
> > >
> > > The way I imagine it now is a special case of the ~ function.
> > > I create matchgroups in a table and check each character if it is in the
> > > group. If it is I will replace the character with the group in [éÉE],
> > > [oóOÓ??] and do a regexp with that.
> >
> > No need to reinvent the wheel. ICU provides a range of services to deal
> > with this. For example the following filter in ICU:
> >
> > NFD; [:Nonspacing Mark:] Remove; NFC.
> >
> > Will remove all accents from characters. And it works for all Unicode
> > characters. With a bit more thinking you can work with case variations
> > also.
> >
> > There is also a locale-independant case-mapping module there plus
> > various locale specific ones also.
> >
> > http://icu.sourceforge.net/userguide/Transform.html
> > http://icu.sourceforge.net/userguide/caseMappings.html
> > http://icu.sourceforge.net/userguide/normalization.html
> >
> > Have a nice day,
> >
> Thanks, I looked at this and it looks like something that would indeed
> solve the problem.
> However I was so far unable to figure out how could I use this from
> within Postgres. If you have experience with it could you give me an
> example?
I was looking into creating a Pg function wrapper to some of the ICU
stuff, but, to be perfectly honest, I couldn't find an actual API
reference for ICU.
In any case, you can do this with PL/Perl:
CREATE FUNCTION strip_nonspacing_marks ( text ) RETURNS text AS $func$
use Unicode::Normalize;
use Encode;
my $string = NFD( decode( utf8 => shift() ) );
$string =~ s/\p{Mn}+//ogsm;
return NFC($string);
$func$ LANGUAGE 'plperl' STRICT;
It's untested and won't be as fast as ICU, but it should get the job
done. Hope it helps!
>
> Thanks
> Balázs
>
> ---(end of broadcast)---
> TIP 6: explain analyze is your friend
>
--
Mike Rylander
[EMAIL PROTECTED]
GPLS -- PINES Development
Database Developer
http://open-ils.org
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [GENERAL] postmaster going down own its on
Martijn van Oosterhout writes: > On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote: >> What would be sending SIGTERM to a backend? > The only other thing I've ever heard of is some systems do a sigterm > when you pass a quota limit? Could be. The actual standard use of SIGTERM is to kill processes belonging to your terminal process group when you log out. So, for example, manually starting the postmaster from a terminal window and then closing that window could cause this to happen. I suppose the OP is bright enough to have noticed the connection between closing the window and losing the postmaster, so it's probably not quite that simple, but anyway something like this is what to look for. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] postmaster going down own its on
Tom Lane <[EMAIL PROTECTED]> writes: > Martijn van Oosterhout writes: >> On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote: >>> What would be sending SIGTERM to a backend? > >> The only other thing I've ever heard of is some systems do a sigterm >> when you pass a quota limit? > > Could be. The actual standard use of SIGTERM is to kill processes > belonging to your terminal process group when you log out. So, for > example, manually starting the postmaster from a terminal window and > then closing that window could cause this to happen. I thought that was SIGHUP? -Doug ---(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] postmaster going down own its on
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 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Running Command Line From Trigger?
I'm running postgresql 7.4.1. is it can't really be used for trigger function? http://www.postgresql.org/docs/7.4/static/plperl-missing.html
Re: [GENERAL] Running Command Line From Trigger?
On Fri, 2006-04-07 at 10:42, Yudie Pg wrote: > > > I'm running postgresql 7.4.1. is it can't really be used for trigger > function? > > http://www.postgresql.org/docs/7.4/static/plperl-missing.html > Two points: 1: Upgrade to 7.4.12 (or whatever the latest version is) immediately. There are known data loss bugs in 7.4.1, and usually, the closer you are to 7.4.0, the more likely those kinds of bugs are to show up. I.e. a data loss bug discovered in 7.4.11 and fixed in 7.4.12 is probably REALLY rare, but one found in 7.4.0 and fixed in 7.4.2 is much more likely to be a common occurrence, since those are found early on. 2: Try using plphp. It can be used for triggers. So can pltcl if you'd rather use that. ---(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] Running Command Line From Trigger?
On Fri, 2006-04-07 at 10:42, Yudie Pg wrote: > > > I'm running postgresql 7.4.1. is it can't really be used for trigger > function? > > http://www.postgresql.org/docs/7.4/static/plperl-missing.html > Quick followup, the latest plPHP does not work on Postgresql versions < 8.0. So you'd either need to upgrade your postgresql to run it, or look for pltcl. pltcl has been around a while, so I can't imagine there not being a good, solid, working version for pg 7.4 ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Running Command Line From Trigger?
Yudie Pg wrote: I'm running postgresql 7.4.1. is it can't really be used for trigger function? http://www.postgresql.org/docs/7.4/static/plperl-missing.html That is true, but you can call a plperl function from a plpgsql trigger function. Wouldn't that work? -- Tony Caduto AM Software Design http://www.amsoftwaredesign.com Home of PG Lightning Admin for Postgresql Your best bet for Postgresql Administration ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] Running Command Line From Trigger?
Back to my original question where is it possible to run a command line from a function?
Re: [GENERAL] Running Command Line From Trigger?
On Friday 07 April 2006 01:32 pm, Yudie Pg saith: > Back to my original question where is it possible to run a command line > from a function? From an earlier post: "Note that plpgsql cannot run external programs on purpose. It's a security and safety issue." ---(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] User-defined types
Anyone know of a quick and dirty query that can retrieve the various type definitions ? I am looking to retrieve the schema-equivalent representation of a custom (user-defined) types. ---(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] User-defined types
\dT -DanielOn 4/7/06, codeWarrior <[EMAIL PROTECTED]> wrote: Anyone know of a quick and dirty query that can retrieve the various typedefinitions ? I am looking to retrieve the schema-equivalent representationof a custom (user-defined) types.---(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] Running Command Line From Trigger?
On Fri, 2006-04-07 at 12:38, Terry Lee Tucker wrote: > On Friday 07 April 2006 01:32 pm, Yudie Pg saith: > > Back to my original question where is it possible to run a command line > > from a function? > > From an earlier post: > "Note that plpgsql cannot run external programs on purpose. It's a > security and safety issue." Which is why I had advised using another language. Help! We're all trapped in a loop! ahhh! ---(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] Running Command Line From Trigger?
Reminds me of an old Star Trek - Next Generation episode. They were stuck in a time loop reliving the same series of events over and over. They had to leave themselves a clue so they could figure it out next time around. Maybe your post is it ;o) On Friday 07 April 2006 02:12 pm, Scott Marlowe saith: > On Fri, 2006-04-07 at 12:38, Terry Lee Tucker wrote: > > On Friday 07 April 2006 01:32 pm, Yudie Pg saith: > > > Back to my original question where is it possible to run a command line > > > from a function? > > > > From an earlier post: > > "Note that plpgsql cannot run external programs on purpose. It's a > > security and safety issue." > > Which is why I had advised using another language. Help! We're all > trapped in a loop! ahhh! > ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] could not create shared memory segment in Windows XP
On 4/5/06, Andrus <[EMAIL PROTECTED]> wrote: > I'm unable to create database cluster in Windows 2000 server. > > initdb returns error > > FATAL: could not create shared memory segment: No such file or directory > > any idea how to create cluster in Windows 2000 ? are you trying to initdb from terminal services? if so, create a one line batch file containing the initdb startup, and run it with postgres user login. merlin ---(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] User-defined types
"codeWarrior" <[EMAIL PROTECTED]> writes: > Anyone know of a quick and dirty query that can retrieve the various type > definitions ? I am looking to retrieve the schema-equivalent representation > of a custom (user-defined) types. Invoking "pg_dump -s" is by far the most future-proof approach. regards, tom lane ---(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] User-defined types
I figured it out
BTW: I was thinking more along the lines of:
SELECT PT.*, PA.* FROM pg_attribute PA
JOIN pg_type PT ON PA.attrelid = PT.typrelid
JOIN pg_class PC ON PC.oid = PA.attrelid
WHERE PT.typnamespace = 2200 AND PA.attnum > 0 AND PC.relkind IN ('r', 'c',
'v');
Perhaps this should be made into a view in the information_schema.
Regards,
Gregory P. Patnude
Vice President - Applications & Innovations Group
iDynaTECH, Inc
665 North Riverpoint Blvd
Spokane, WA 99202
(509) 343-3104 [voice]
(208) 691-6198 [cellular]
http://www.idynatech.com
"Tom Lane" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> "codeWarrior" <[EMAIL PROTECTED]> writes:
>> Anyone know of a quick and dirty query that can retrieve the various type
>> definitions ? I am looking to retrieve the schema-equivalent
>> representation
>> of a custom (user-defined) types.
>
> Invoking "pg_dump -s" is by far the most future-proof approach.
>
> regards, tom lane
>
> ---(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
>
---(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] User-defined types
"codeWarrior" <[EMAIL PROTECTED]> writes:
> BTW: I was thinking more along the lines of:
> SELECT PT.*, PA.* FROM pg_attribute PA
> JOIN pg_type PT ON PA.attrelid = PT.typrelid
> JOIN pg_class PC ON PC.oid = PA.attrelid
> WHERE PT.typnamespace = 2200 AND PA.attnum > 0 AND PC.relkind IN ('r', 'c',
> 'v');
> Perhaps this should be made into a view in the information_schema.
It seems like the COLUMN_UDT_USAGE view ought to handle this ...
except perhaps that COLUMN_UDT_USAGE for some reason substitutes the
underlying type if the column type is a domain. I can't see the
justification for that --- Peter, what part of the spec led you to do
it that way? There is probably more than one way to define the spec's
notion of "user-defined types" in terms of Postgres notions, but I
don't see where you got this particular definition.
regards, tom lane
---(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] Running Command Line From Trigger?
Help! Try to install plperl ./createlang plperl mydb createlang: language installation failed: ERROR: could not access file "$libdir/plperl": No such file or directory
Re: [GENERAL] Running Command Line From Trigger?
On Friday 07 April 2006 03:52 pm, Yudie Pg saith: > Help! > Try to install plperl > ./createlang plperl mydb > > createlang: language installation failed: ERROR: could not access file > "$libdir/plperl": No such file or directory Do you have the Perl module on your machine? If not, you can get it here: http://search.cpan.org/search?query=Pg&mode=all ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] pgAdmin3 question
Hi All, Have a question on pgAdmin3: 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? As the Maintenance DB dropdown box doesn't show this test db, we have to allow the owner of this test db (a new user created for this test db only) to access 'all' database in the pg_hba.conf file in order to allow it to login through pgAdmin. And once loged in, it of course has access to all databases including the postgres. How can we control this situation through pgAdmin? Any help would be greatly appreciated. Thanks, leo __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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] Debian package for freeradius_postgresql module
lmyho <[EMAIL PROTECTED]> wrote: > > Oh right, they're claiming that they can't distribute freeradius using > > postgresql because postgresql links to OpenSSL. freeradius is GPL which > > makes for an incompatabilty. Not something PostgreSQL is responsible > > for, given Debian could compile without SSL and the problem would be > > solved. OK, I'm kind of confused about how the legal red tape works here. Debian packages all sorts of GPL code, and both openssl and postgres are released under more liberal licenses. About the only legal issue I could see is the legalities surrounding the export of openssl, but I thought debian had already found it's own way around that. > > About the only thing we could do is support GnuTLS, but that's about > > it. I'm in love with debian, so if that's what it takes to get a package people find useful in there, I'm all for it. > It's just a little complicated for a common user like me. But if it can be > solved by just going a bit harder way, like to make a debian package by > our own, that's ok too, as long as we don't have to switch the os to make > the two work together. You may not even need to do that; http://www1.apt-get.org/search.php?query=freeradius&submit=Submit+Query&arch%5B%5D=i386&arch%5B%5D=all The second search result there includes two sets of /etc/apt/sources.list lines that both provide freeradius-postgresql. Cheers, Tyler ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] pgAdmin3 question
> 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. Those databases are just helpful defaults. > As the Maintenance DB dropdown box doesn't show this test db, we have to > allow the > owner of this test db (a new user created for this test db only) to access > 'all' > database in the pg_hba.conf file in order to allow it to login through > pgAdmin. And > once loged in, it of course has access to all databases including the > postgres. How > can we control this situation through pgAdmin? No, you don't have to allow access to all databases. You can type the name of the preferred maintenance DB, or grant the user access to 'postgres' as well as any other databases they need. 'postgres' is intended for this sort of use... Regards, Dave -Unmodified Original Message- Hi All, Have a question on pgAdmin3: 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? As the Maintenance DB dropdown box doesn't show this test db, we have to allow the owner of this test db (a new user created for this test db only) to access 'all' database in the pg_hba.conf file in order to allow it to login through pgAdmin. And once loged in, it of course has access to all databases including the postgres. How can we control this situation through pgAdmin? Any help would be greatly appreciated. Thanks, leo __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] pgAdmin3 question
--- Dave Page 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? > > As the Maintenance DB dropdown box doesn't show this test db, we have to > > allow > the > > owner of this test db (a new user created for this test db only) to access > > 'all' > > database in the pg_hba.conf file in order to allow it to login through > > pgAdmin. > And > > once loged in, it of course has access to all databases including the > > postgres. > How > > can we control this situation through pgAdmin? > > No, you don't have to allow access to all databases. You can type the name of > the > preferred maintenance DB, Yea! Worked by typing the new db name! Sorry didn't notice that we can type a name into the dropdown box.:( Thank you! 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. What has I done wrong? Or how should I use the "ident" authen way through pgAdmin? Thank you for your help!! regards, leo __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] Creating a trigger on n tables?
Is there an easier way to create the same trigger for n tables or do I need to run create trigger n times? Regards, BTJ -- --- Bjørn T Johansen [EMAIL PROTECTED] --- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" --- ---(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] Debian package for freeradius_postgresql module
Tyler MacDonald <[EMAIL PROTECTED]> writes: > OK, I'm kind of confused about how the legal red tape works here. > Debian packages all sorts of GPL code, and both openssl and postgres are > released under more liberal licenses. About the only legal issue I could see > is the legalities surrounding the export of openssl, but I thought debian > had already found it's own way around that. [ looks in openssl tarball... ] It looks like the openssl license is essentially old-style BSD (ie, with advertising clause). If Debian is being anal about refusing to ship old-BSD code linked to GPL code, there's going to be a whole lot of stuff that doesn't support SSL on Debian, not only Postgres. Or are they selectively enforcing this policy against PG? (FWIW, Red Hat doesn't seem to be worried about this ... you could always migrate to Fedora ;-)) regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Debian package for freeradius_postgresql module
Tom Lane <[EMAIL PROTECTED]> writes: > Tyler MacDonald <[EMAIL PROTECTED]> writes: >> OK, I'm kind of confused about how the legal red tape works here. >> Debian packages all sorts of GPL code, and both openssl and postgres are >> released under more liberal licenses. About the only legal issue I could see >> is the legalities surrounding the export of openssl, but I thought debian >> had already found it's own way around that. > > [ looks in openssl tarball... ] It looks like the openssl license is > essentially old-style BSD (ie, with advertising clause). If Debian is > being anal about refusing to ship old-BSD code linked to GPL code, > there's going to be a whole lot of stuff that doesn't support SSL on > Debian, not only Postgres. Or are they selectively enforcing this > policy against PG? I don't think so. I got curious and looked at what's on my Ubuntu system: Courier IMAP is GPL with an additional clause that explicitly allows linking with OpenSSL; Postfix has an Apache-ish license; Exim is GPL and also explicitly allows linking with OpenSSL; Cyrus IMAP is BSDish; Apache is non-GPL... I can't think offhand of anything that is GPL and links with OpenSSL without an explicit clause permitting same. -Doug ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Debian package for freeradius_postgresql module
Douglas McNaught <[EMAIL PROTECTED]> writes: > I don't think so. I got curious and looked at what's on my Ubuntu > system: Courier IMAP is GPL with an additional clause that explicitly > allows linking with OpenSSL; Postfix has an Apache-ish license; Exim > is GPL and also explicitly allows linking with OpenSSL; Cyrus IMAP is > BSDish; Apache is non-GPL... I can't think offhand of anything that > is GPL and links with OpenSSL without an explicit clause permitting > same. Hm. So can we lobby freeradius to tweak their license similarly? 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, 2006-04-07 at 17:08, Tom Lane wrote: > Douglas McNaught <[EMAIL PROTECTED]> writes: > > I don't think so. I got curious and looked at what's on my Ubuntu > > system: Courier IMAP is GPL with an additional clause that explicitly > > allows linking with OpenSSL; Postfix has an Apache-ish license; Exim > > is GPL and also explicitly allows linking with OpenSSL; Cyrus IMAP is > > BSDish; Apache is non-GPL... I can't think offhand of anything that > > is GPL and links with OpenSSL without an explicit clause permitting > > same. > > Hm. So can we lobby freeradius to tweak their license similarly? I thought from Douglas' message, it appeared BSD packages didn't need such a clause... ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Debian package for freeradius_postgresql module
Scott Marlowe <[EMAIL PROTECTED]> writes: > I thought from Douglas' message, it appeared BSD packages didn't need > such a clause... GPL partisans feel that BSD-with-advertising-clause is not compatible with the GPL. I think the sticking point here is that openssl is using an advertising clause. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Allow linking against OpenSSL? (Was Re: [GENERAL] Debian package for freeradius_postgresql module)
Greetings FreeRadius people, This discussion started on the postgresql's "pgsql-general" mailing list. The problem here is that the freeradius-postgresql package needs to link against libpgsql, which means that it may be indirectly linked against openssl. There is a conflict between OpenSSL's BSD license and the GPL which means that it's not legal to distribute a copy of GPL code that is linked in this way. It appears that several other GPL apps have added a special clause to their license that allows them to be linked against OpenSSL. Could this be done for freeradius/freeradius-postgresql as well? This could pave the way towards enhanced freeradius support in Debian, specifically the addition of freeradius-postgresql to Debian's mainline. For your reference, here is the start of the thread on the pgsql-general list that got us to this point: http://archives.postgresql.org/pgsql-general/2006-04/msg00247.php Thanks, Tyler Tom Lane <[EMAIL PROTECTED]> wrote: > > I don't think so. I got curious and looked at what's on my Ubuntu > > system: Courier IMAP is GPL with an additional clause that explicitly > > allows linking with OpenSSL; Postfix has an Apache-ish license; Exim > > is GPL and also explicitly allows linking with OpenSSL; Cyrus IMAP is > > BSDish; Apache is non-GPL... I can't think offhand of anything that > > is GPL and links with OpenSSL without an explicit clause permitting > > same. > Hm. So can we lobby freeradius to tweak their license similarly? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] Debian package for freeradius_postgresql module
On Fri, 2006-04-07 at 17:16, Tom Lane wrote: > Scott Marlowe <[EMAIL PROTECTED]> writes: > > I thought from Douglas' message, it appeared BSD packages didn't need > > such a clause... > > GPL partisans feel that BSD-with-advertising-clause is not compatible > with the GPL. I think the sticking point here is that openssl is using > an advertising clause. But the way Douglas' message read, it was only GPL packages that should be affected, and we're not GPL. Or did I or Douglas misunderstand the situation? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: Allow linking against OpenSSL? (Was Re: [GENERAL] Debian
On Fri, 2006-04-07 at 17:24, Tyler MacDonald wrote: > Greetings FreeRadius people, > > This discussion started on the postgresql's "pgsql-general" mailing > list. The problem here is that the freeradius-postgresql package needs to > link against libpgsql, which means that it may be indirectly linked against > openssl. There is a conflict between OpenSSL's BSD license and the GPL which > means that it's not legal to distribute a copy of GPL code that is linked in > this way. It appears that several other GPL apps have added a special clause > to their license that allows them to be linked against OpenSSL. > > Could this be done for freeradius/freeradius-postgresql as well? > This could pave the way towards enhanced freeradius support in Debian, > specifically the addition of freeradius-postgresql to Debian's mainline. > > For your reference, here is the start of the thread on the > pgsql-general list that got us to this point: > > http://archives.postgresql.org/pgsql-general/2006-04/msg00247.php Please note that PostgreSQL is NOT GPL, but BSD. Just sayin' ---(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
Scott Marlowe <[EMAIL PROTECTED]> wrote: > > GPL partisans feel that BSD-with-advertising-clause is not compatible > > with the GPL. I think the sticking point here is that openssl is using > > an advertising clause. > > But the way Douglas' message read, it was only GPL packages that should > be affected, and we're not GPL. Or did I or Douglas misunderstand the > situation? It's freeradius that's GPL. Then we break GPL rules by importing OpenSSL. Guilt by association. :) - Tyler ---(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] can we remove this guy from the list?
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
Re: [GENERAL] Debian package for freeradius_postgresql module
Tyler MacDonald wrote: Scott Marlowe <[EMAIL PROTECTED]> wrote: But the way Douglas' message read, it was only GPL packages that should be affected, and we're not GPL. Or did I or Douglas misunderstand the situation? It's freeradius that's GPL. Then we break GPL rules by importing OpenSSL. Guilt by association. :) IANAL, but this seems pretty problematic an interpretation of the GPL. 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. What really seems to be happening here is that the Debian community seems to be taking a stand which has little to do with the wording of the GPL and more of an issue of "we don't like what NVidia is doing wrt Linux drivers, so we are going to implement a policy that prevents it." We are, unfortunately, caught in the crossfire. My own opinion is this: The Debian crowd are often technical enough they can build whatever they want from source. Debian is a niche distribution and not something we should spend too much time worrying about whether our software can be indirectly linked with GPL apps on their site. BTW, does this also mean that no GNU Readline is available in the Debian versions of psql? Or am I missing something? Best Wishes, Chris Travers Metatron Technology Consulting ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] Debian package for freeradius_postgresql module
Chris Travers <[EMAIL PROTECTED]> wrote: > My own opinion is this: The Debian crowd are often technical enough > they can build whatever they want from source. Debian is a niche > distribution and not something we should spend too much time worrying > about whether our software can be indirectly linked with GPL apps on > their site. Debian a niche distribution? I'd hardly call the defacto standard GNU Linux distribution a "niche"... > BTW, does this also mean that no GNU Readline is available in the Debian > versions of psql? Or am I missing something? AFAIK psql doesn't have the BSD advertising clause (does it??)... and that's the piece that's incompatible with the GPL. Cheers, Tyler ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] plgpsql and transactions
On Thu, Apr 06, 2006 at 03:48:15PM -0500, Terry Lee Tucker wrote: > > > > -- fires a trigger that updates more than one table > > insert into semething (default); > > > > and: > > > > begin; > > -- fires a trigger that updates more than one table > > insert into somthing (default); > > commit; > > > > In the latter, you have expanded the scope of the transaction; which, > sometimes you might want to do. Yes, I might. But, I'd like to understand it so I do know when I might or might not want to do it. Say I have a BEFORE INSERT trigger that does a table lock. When is that lock released? At the end of the trigger? Or after the INSERT has completed? For example, say I want to set a column on the row I'm inserting based on what's already in the table. So I lock the table in the trigger and check the current status of the table and set the column based on that current status. I want to make sure that between the time the trigger completes and when the insert finally happens that another session can't also do an insert and see the same table state. -- Bill Moseley [EMAIL PROTECTED] ---(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] Debian package for freeradius_postgresql module
On Saturday 08 April 2006 01:21, Tyler MacDonald wrote: >Debian a niche distribution? I'd hardly call the defacto standard >GNU Linux distribution a "niche"... Surely, Debian is "niche". Why else should there be a need for distributions like Gentoo? I once tried to run Debian, and asked for help on some probably elementary question on the Debian users list. All I got in the way of help was "read the f*ing manual". Sure, very helpful indeed. Later, I installed Gentoo and was positively amazed at the level of help you would get on the Gentoo-forum. I never looked back to Debian. -- Leif Biberg Kristensen | Registered Linux User #338009 http://solumslekt.org/ | Cruising with Gentoo/KDE ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] plgpsql and transactions
> > > > In the latter, you have expanded the scope of the transaction; which, > > sometimes you might want to do. > > Yes, I might. But, I'd like to understand it so I do know when I might > or might not want to do it. Understanding is good. You need to read the documentation on transactions: http://www.postgresql.org/docs/7.4/interactive/tutorial-transactions.html and Concurrency control: http://www.postgresql.org/docs/7.4/interactive/mvcc.html > > Say I have a BEFORE INSERT trigger that does a table lock. When > is that lock released? At the end of the trigger? Or after the > INSERT has completed? At the end of the transaction. > > For example, say I want to set a column on the row I'm inserting based > on what's already in the table. So I lock the table in the trigger > and check the current status of the table and set the column based on > that current status. > > I want to make sure that between the time the trigger completes and > when the insert finally happens that another session can't also do an > insert and see the same table state. Again, reading the docs on concurrency control and transactions will answer these questions. > > > > -- > Bill Moseley > [EMAIL PROTECTED] > > > ---(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 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] Debian package for freeradius_postgresql module
* Tom Lane ([EMAIL PROTECTED]) wrote: > Tyler MacDonald <[EMAIL PROTECTED]> writes: > > OK, I'm kind of confused about how the legal red tape works here. > > Debian packages all sorts of GPL code, and both openssl and postgres are > > released under more liberal licenses. About the only legal issue I could see > > is the legalities surrounding the export of openssl, but I thought debian > > had already found it's own way around that. > > [ looks in openssl tarball... ] It looks like the openssl license is > essentially old-style BSD (ie, with advertising clause). If Debian is > being anal about refusing to ship old-BSD code linked to GPL code, > there's going to be a whole lot of stuff that doesn't support SSL on > Debian, not only Postgres. Or are they selectively enforcing this > policy against PG? It's enforced whenever we discover it, really... Alot of applications are able to be built against GNUTLS which is LGPL and removes the issue as well. Debian actually worked to port OpenLDAP to GNUTLS to deal with this problem with all of the (quite a few...) GPL'd LDAP-using applications we package. I was involved in that effort actually (though didn't actually do the GNUTLS port, that was mainly done by Steve Langasek). I'd like to look into doing this for Postgres, actually... I don't think it'd hurt for Postgres to support OpenSSL and GNUTLS. Thanks, Stephen signature.asc Description: Digital signature
Re: [GENERAL] Debian package for freeradius_postgresql module
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. 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. regards, tom lane ---(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] Debian package for freeradius_postgresql module
* Tom Lane ([EMAIL PROTECTED]) wrote: > 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. Feel free to. > 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. I don't feel it's a questionable reading of the GPL at all. In fact, it's pretty clear and I'm about 99% sure the FSF has commented on this as well. It's true that it's unlikely anyone would actually sue Debian over it but that doesn't somehow change what the licenses say. Additionally, I think supporting GNUTLS would be a good thing for Postgres to do even without this issue. I'd also like to see it support SASL and a k5login-style user-controllable mapping. Thanks, Stephen signature.asc Description: Digital signature
Re: [GENERAL] Debian package for freeradius_postgresql module
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes: > On Saturday 08 April 2006 01:21, Tyler MacDonald wrote: >>Debian a niche distribution? I'd hardly call the defacto standard >>GNU Linux distribution a "niche"... > > Surely, Debian is "niche". Why else should there be a need for > distributions like Gentoo? > > I once tried to run Debian, and asked for help on some probably > elementary question on the Debian users list. All I got in the way of > help was "read the f*ing manual". Sure, very helpful indeed. Later, I > installed Gentoo and was positively amazed at the level of help you > would get on the Gentoo-forum. I never looked back to Debian. You can dislike it all you want (and I'm not saying you don't have reason to), but Debian is *not* "niche". There are a *lot* of servers out there running it, and it's also the basis for Ubuntu, which by itself is at least as popular as Gentoo from what I can see. On the server side, I'd put Debian in the top three along with RH and SuSE. Even if the mailing lists are unfriendly. But we're wandering off-topic. :) -Doug ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] MediaWiki and Postgresql?
On Thursday 06 April 2006 16:45, Jim Nasby wrote:
> On Apr 4, 2006, at 11:08 AM, Scott Marlowe wrote:
> > On Mon, 2006-04-03 at 06:36, Markus Wollny wrote:
> >> Hi
> >>
> >> [EMAIL PROTECTED] wrote:
> >>> Has anyone put MediaWiki up using the current version of Postgresql?
> >>
Most of the code I have seen has been run against pg 8.0.x or 8.1.x; generally
pg isnt the problem in this equation.
> >> I have, although our Mediawiki installation is currently not openly
> >> accessible. Can't say that it went like a breeze, but the obstacles
> >> where more or less minor and writing a little custom auth-plugin
> >> wasn't
> >> really too hard either. If your question was just along the lines of
> >> "does it run", I can confirm that, yes, it does. I cannot say
> >> though how
> >> well it would stand up to high loads and if every query and index has
> >> been fully tweaked.
> >
I know a few people running postgresql based mediawiki installations and it
seems to hold up pretty nicely. These folks aren't running the same code you
would find at the core mediawiki project, but instead they are using
patched/modified code to get things working. A fairly runnable copy is the
0.0.3 release of wikipgedia, though it too needs a few security updates from
the core project. You could probably get the cvs code working again, though
it needs testing and probably some fixes.
> > Given that this page:
> >
> > http://www.mediawiki.org/wiki/Help:%24wgDBtype
> >
> > says:
> >
> > Use ""mysql"" for working code and ""PostgreSQL"" for development/
> > broken
> > code.
> >
> > I'd guess that PostgreSQL support is not quite at the same level as
> > MySQL just yet. :)
>
I think this is a fairly good summary of things:
http://lists.pgfoundry.org/pipermail/wikipedia-news/2006-February/17.html
> If I'm not confusing wiki's (and I'm offline now, so I can't check),
> Mediawiki is pretty un-interested in supporting PostgreSQL (hard to
> imagine why, given that some of their folks are paid by MySQL AB), so
> a fork was created on pgFoundry. I believe it's called pgpedia.
>
> If I am confusing wiki's, I'm wondering if they'd be willing to
> accept patches to improve PostgreSQL support...
You are not. I dubbed the new code wikipgedia, it lives on the foundry, the
home page is at http://wikipedia.projects.postgresql.org/. We would love to
have some new contributors. I hope to give another go around at making the
code production ready, but it involves the properly shaped tuits, and I don't
have a database company paying me to work on it :-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [GENERAL] Debian package for freeradius_postgresql module
On Fri, 2006-04-07 at 19:13, Stephen Frost wrote: > * Tom Lane ([EMAIL PROTECTED]) wrote: > > 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. > > Feel free to. > > > 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. > > I don't feel it's a questionable reading of the GPL at all. In fact, > it's pretty clear and I'm about 99% sure the FSF has commented on this > as well. It's true that it's unlikely anyone would actually sue Debian > over it but that doesn't somehow change what the licenses say. > Additionally, I think supporting GNUTLS would be a good thing for > Postgres to do even without this issue. I'd also like to see it support > SASL and a k5login-style user-controllable mapping. So, do GPL have this problem linking against OpenSSL as well? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] Debian package for freeradius_postgresql module
Scott Marlowe <[EMAIL PROTECTED]> writes: >> I don't feel it's a questionable reading of the GPL at all. In fact, >> it's pretty clear and I'm about 99% sure the FSF has commented on this >> as well. It's true that it's unlikely anyone would actually sue Debian >> over it but that doesn't somehow change what the licenses say. >> Additionally, I think supporting GNUTLS would be a good thing for >> Postgres to do even without this issue. I'd also like to see it support >> SASL and a k5login-style user-controllable mapping. > > So, do GPL have this problem linking against OpenSSL as well? Yes, that's why GPL apps like Exim and Courier have explicit license clauses permitting it. -Doug ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Debian package for freeradius_postgresql module
On Fri, 2006-04-07 at 19:31, Douglas McNaught wrote: > Scott Marlowe <[EMAIL PROTECTED]> writes: > > >> I don't feel it's a questionable reading of the GPL at all. In fact, > >> it's pretty clear and I'm about 99% sure the FSF has commented on this > >> as well. It's true that it's unlikely anyone would actually sue Debian > >> over it but that doesn't somehow change what the licenses say. > >> Additionally, I think supporting GNUTLS would be a good thing for > >> Postgres to do even without this issue. I'd also like to see it support > >> SASL and a k5login-style user-controllable mapping. > > > > So, do GPL have this problem linking against OpenSSL as well? > > Yes, that's why GPL apps like Exim and Courier have explicit license > clauses permitting it. So, it's freeradius that needs the exception then, right? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: Allow linking against OpenSSL? (Was Re: [GENERAL] Debian package for freeradius_postgresql module)
Alan DeKok <[EMAIL PROTECTED]> wrote: > > It appears that several other GPL apps have added a special clause > > to their license that allows them to be linked against OpenSSL. > > > > Could this be done for freeradius/freeradius-postgresql as well? > > I have no objection to that. > > Debian should at least be able to distribute their version of source > packages, that will build binaries against the distributed binary packages. > > Alan DeKok. Thanks Alan!!! Can we look forward to this clause in the next version of FreeRadius? Is the next version due to come out anytime soon? Thanks, Tyler ---(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: Allow linking against OpenSSL? (Was Re: [GENERAL] Debian package
Tyler MacDonald wrote: Greetings FreeRadius people, This discussion started on the postgresql's "pgsql-general" mailing list. The problem here is that the freeradius-postgresql package needs to link against libpgsql, which means that it may be indirectly linked against openssl. There is a conflict between OpenSSL's BSD license and the GPL which means that it's not legal to distribute a copy of GPL code that is linked in this way. It appears that several other GPL apps have added a special clause to their license that allows them to be linked against OpenSSL. IANAL, but I don't think that this argument flies. I don't think that indirect linking constitutes derivation. Indeed I don't think that linking constitutes derivation absent other factors. At least in the 9th Circuit, you have the Gates test (Gates Rubber, not Bill Gates), which might well suggest that linking is *not* derivation at least in this jurisdiction. Generally for one work to be a derivative of another, you have to have some degree of derivation which is evident. This need not be literal copying. But hte line migh be quite fuzzy-- for example, a program which makes extensive use of a non-standard Windows API might be argued to be a derivative work of Windows (MySQL used to make a similar argument regarding dependance on their client libraries, so this is not that far fetched). The direction Debian is taking this seems rediculous in the extreme-- that one might need a license to develop software for Windows, just like you would if you wanted to use MySQL only via ODBC 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 5: don't forget to increase your free space map settings
Re: [GENERAL] Debian package for freeradius_postgresql module
Scott Marlowe <[EMAIL PROTECTED]> wrote: > > >> I don't feel it's a questionable reading of the GPL at all. In fact, > > >> it's pretty clear and I'm about 99% sure the FSF has commented on this > > >> as well. It's true that it's unlikely anyone would actually sue Debian > > >> over it but that doesn't somehow change what the licenses say. > > >> Additionally, I think supporting GNUTLS would be a good thing for > > >> Postgres to do even without this issue. I'd also like to see it support > > >> SASL and a k5login-style user-controllable mapping. > > > > > > So, do GPL have this problem linking against OpenSSL as well? > > > > Yes, that's why GPL apps like Exim and Courier have explicit license > > clauses permitting it. > > So, it's freeradius that needs the exception then, right? Good morning Scott, would you like some coffee? :-) - Tyler ---(end of broadcast)--- TIP 6: explain analyze is your friend
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
