-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reinhard Max wrote: > On Fri, 3 Aug 2007 at 19:09, Jorge Godoy wrote: > >> Having updated packages would be great! Specially if they would be >> updated for, e.g., OpenSuSE 10.1 and OpenSuSE 10.2 (both already >> released) and not just for OpenSuSE 10.3 (still under >> "development"). > > Yes, that's why I created the /pub/projects/postgresql directory on > ftp.suse.com, but I have to admit that I got a bit lazy in keeping it > up to date. > > I've just built and uploaded the 8.2.4 package from to-be 10.3 for > 10.2, 10.1/SLES10, 10.0, 9.3, and 9.1/SLES9: > > ftp://ftp.suse.com/pub/projects/postgresql/postgresql-8.2.4 > > My mid-term plan (for when the dust of 10.3 has settled) is to close > the /pub/projects/postgresql directory and offer these packages in the > openSUSE buildservice instead, so that others can participate and help > improving the packages and keeping them up to date. Hmmm, it seems that this would be also suited to be in the PostgreSQL.Org archives yes? Joshua D. Drake > > cu > Reinhard > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your > message can get through to the mailing list cleanly > - -- === 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGt0u+ATb/zqfZUUQRArcyAJ98hDS3L/WIQVh9+m7K9UrJkNYbaQCgoPLS VvODkWQsn/qXFU/+nQG+GGY= =JQam -----END PGP SIGNATURE----- ---------------------------(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
