Re: [pgadmin-hackers] pgadmin3.chm in CVS
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 09 September 2003 21:14 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] pgadmin3.chm in CVS > > > Dave Page wrote: > > >Hi Andreas, > > > >After a particularly painful CVS update, I have removed pgadmin3.chm > >from CVS. As you know, it's a large compiled file, only useful to > >Windows users, > > > This will change very soon, there's a wx implementation for > gtk on the way. There are already contribs that can do it, > and a patch is pending to > have it in wx2.5 > > IMHO, we need a download location for "misc. binaries" for *.chm and > *.mo. We don't need versions for any of them. I have no problem with that at all - please feel free to create something in the snapshots or ftp areas, or let me know what you want and I'll do it. For the .mo files however, I think there are valid reasons to keep them in CVS: 1) They are very small. 2) They are needed by all builds and distributions. 3) There is no simple method to compile them as part of the build process (particularly on Windows). (Yes, I know this point is arguable). Regards, Dave. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] dlgOperator_patch
> -Original Message- > From: Hiroshi Saito [mailto:[EMAIL PROTECTED] > Sent: 10 September 2003 03:24 > To: Dave Page > Cc: [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] dlgOperator_patch > > > > This is one that is not in pga2 - any ideas? > > MERGES is specified tacitly. > Default name in the preparation is put. > I don't think that it is a problem that it doesn't have > chkbox. I think it has as much right to be there as HASHES, however whilst there is a oprcanhash column in pg_operator, there is no oprcanmerge column. So what defines a mergeable operator? > However, are LTCMP, GTCMP necessary? Yes, I think so. You can specify them when you create an operator (they are shown as < operator and > operator btw.). Regards, Dave. ---(end of broadcast)--- TIP 8: explain analyze is your friend
[pgadmin-hackers] ./configure patch needed to build portable SRPMs
Dear all, To make a portable SRPM (which would rebuild on any platform) we need the ./configure script to search for "--with-pgsql-include" variable in /usr/include and /usr/include/pgsql (without having to specify it). Otherwise, there will be one SRPM for RedHat and Mandrake and another for SuSE 8.2. Could someone kindly modify the ./configure script? Cheers, Jean-Michel Pouré ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] ./configure patch needed to build portable SRPMs
Dear Jean-Michel, you could also try something like this: ./configure --with-pgsql-include '/usr/include/pgsql -I /usr/include' ... in your spec file. Cheers, Raphaël Message d'origine >De: Jean-Michel POURE <[EMAIL PROTECTED]> >A: <[EMAIL PROTECTED]> >Sujet: [pgadmin-hackers] ./configure patch needed to build portable SRPMs >Date: Wed, 10 Sep 2003 15:57:40 +0200 > >Dear all, > >To make a portable SRPM (which would rebuild on any platform) we need the >../configure script to search for "--with-pgsql-include" variable in >/usr/include and /usr/include/pgsql (without having to specify it). > >Otherwise, there will be one SRPM for RedHat and Mandrake and another for SuSE >8.2. Could someone kindly modify the ./configure script? > >Cheers, >Jean-Michel Pouré > > >---(end of broadcast)--- >TIP 8: explain analyze is your friend > > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] ./configure patch needed to build portable SRPMs
Le Mercredi 10 Septembre 2003 20:51, [EMAIL PROTECTED] a écrit : > ./configure --with-pgsql-include '/usr/include/pgsql -I /usr/include' ... Thanks!!! ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] ./configure patch needed to build portable
Jean-Michel POURE wrote: Dear all, To make a portable SRPM (which would rebuild on any platform) we need the ./configure script to search for "--with-pgsql-include" variable in /usr/include and /usr/include/pgsql (without having to specify it). Otherwise, there will be one SRPM for RedHat and Mandrake and another for SuSE 8.2. Could someone kindly modify the ./configure script? Cheers, Jean-Michel Pouré ---(end of broadcast)--- TIP 8: explain analyze is your friend Attached is a patch that will do what you ask. Or you can use Raphaël's solution. :-) ahp --- pgadmin3/acinclude.m4 2003-08-24 20:44:17.0 -0400 +++ pgadmin3.new/acinclude.m4 2003-09-10 12:21:26.0 -0400 @@ -81,6 +81,15 @@ LIBPQ_HOME=/usr fi fi +if test -f "/usr/include/libpq-fe.h" +then +pgsql_include="/usr/include" +else +if test -f "/usr/include/pgsql/libpq-fe.h" +then +pgsql_include="/usr/include/pgsql" +fi +fi fi ]) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[pgadmin-hackers] autoconf compiling *.c
Hi Adam, for support of keyword checking, we need to include keywords.c. I added this to makefile.am, but the compile flags will lacke the including of the main include dir (../src/include in my build). While we have agreed not to activate this for the 1.0 release, we'll need this quite soon. Please have a look where to add the options so we can compile *.c successfully. Regards, Andreas ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] ./configure patch needed to build portable
Title: Message Thanks Adam, patch applied. Regards, Dave. -Original Message-From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] Sent: 10 September 2003 17:36To: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: Re: [pgadmin-hackers] ./configure patch needed to build portableJean-Michel POURE wrote: Dear all, To make a portable SRPM (which would rebuild on any platform) we need the ./configure script to search for "--with-pgsql-include" variable in /usr/include and /usr/include/pgsql (without having to specify it). Otherwise, there will be one SRPM for RedHat and Mandrake and another for SuSE 8.2. Could someone kindly modify the ./configure script? Cheers, Jean-Michel Pouré ---(end of broadcast)--- TIP 8: explain analyze is your friend Attached is a patch that will do what you ask. Or you can use Raphaël's solution. :-)ahp
Re: [pgadmin-hackers] autoconf compiling *.c
Andreas Pflug wrote: Hi Adam, for support of keyword checking, we need to include keywords.c. I added this to makefile.am, but the compile flags will lacke the including of the main include dir (../src/include in my build). While we have agreed not to activate this for the 1.0 release, we'll need this quite soon. Please have a look where to add the options so we can compile *.c successfully. Regards, Andreas I'm not sure I quite understand; what happens when you add db/keywords.c to Makefile.am, run bootstrap, re-run configure, and re-compile? ahp ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] autoconf compiling *.c
Adam H. Pendleton wrote: Andreas Pflug wrote: Hi Adam, for support of keyword checking, we need to include keywords.c. I added this to makefile.am, but the compile flags will lacke the including of the main include dir (../src/include in my build). While we have agreed not to activate this for the 1.0 release, we'll need this quite soon. Please have a look where to add the options so we can compile *.c successfully. Regards, Andreas I'm not sure I quite understand; what happens when you add db/keywords.c to Makefile.am, run bootstrap, re-run configure, and re-compile? Hi Adam, if I do that, the private includes are not found. Regards, Andreas ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] dlgOperator_patch
Hi Dave. This is patch of pga3. Please Apply it. pga2 is thought to want to adjust it tonight. Regards, Hiroshi Saito From: "Dave Page" <[EMAIL PROTECTED]> > > This is one that is not in pga2 - any ideas? > > MERGES is specified tacitly. > Default name in the preparation is put. > I don't think that it is a problem that it doesn't have > chkbox. I think it has as much right to be there as HASHES, however whilst there is a oprcanhash column in pg_operator, there is no oprcanmerge column. So what defines a mergeable operator? > However, are LTCMP, GTCMP necessary? Yes, I think so. You can specify them when you create an operator (they are shown as < operator and > operator btw.). Regards, Dave. dlgOperator_merge_patch Description: Binary data ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
