Re: [Server-devel] PostgreSQL mgmt on Fedora: pg_cluster-like tools?
On Thu, 2008-09-11 at 20:38 -0400, Tom Lane wrote: Has anyone looked at whether their solution would drop into Fedora? As you'll remember, you and I talked about this issue at PostgreSQL Anniversary Summit. I have worked on a prototype then: https://projects.commandprompt.com/public/pgcore/repo/rpm/redhat/8.1/postgresql/F-9/postgresql-8.1-multiple.spec This is WIP solution, but what we talked then was: * Debian's solution was not that much good. It is built on lots of perl scripts, etc, and maintenance costs are high. * Use the approach that is in the spec file above * Create a postgresql-default-$VERSION package which will make that version default. * Use sysconfig/pgsql file as the main source around multiple postmaster configuration. I will now ask Command Prompt whether they can let me work on this issue for 8.4. This time I started 8.4 very much earlier than we all did before, so I believe, if I have enough time, I can finish this before 8.4 beta and we can apply it to Fedora 11 and above.. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] PostgreSQL mgmt on Fedora: pg_cluster-like tools?
On Fri, 2008-09-12 at 11:59 +1200, Martin Langhoff wrote: - Major Pg upgrades will have to run 100% unattended, with a sane failover, so: install the new version of Pg, attempt a pg_dump|pg_restore data migration and only switch over if it was successful. I am *very* against this one. It is not packager's job to run dump/reload: * You may never be sure that it will work. We had this issue in 8.3 for example. * Upstream never ever gives such a guarantee that all apps will work on every PostgreSQL version. For example, some casts were removed in 8.3. So dumping/restoring should be a DBA work. So switch over if it was successful is really a bad idea, and *will* break things. * RPMs are *not* allowed to do interactive job, per guidelines. Period. Regards, -- Devrim GÜNDÜZ, RHCE devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org signature.asc Description: This is a digitally signed message part ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Want to package PostgreSQL for OLPC
On Wed, 2008-06-25 at 08:48 -0400, Martin Langhoff wrote: How hard is it to get a backport of Pg8.2/8.3, plus some key dependencies (php-pgsql, python-pgsql, pam-pgsql) recompiled to use the new libpq, all on F7? http://yum.pgsqlrpms.org ;) I have already built all PG combinations against Fedora 7-8-9 and RHEL 4,5. We have compat packages, and all pam-pgsql, etc in that repository. So, using those files won't be a problem. Also - I see you work at CommandPrompt -- so I'll throw a wishlist item I have on my list in your direction. Perhaps you, or someone at CommandPrompt has something similar. With Pg packaged, what we will need to come up with is ~3 sets of config files tuned for different memory footprints. The same XS image will be used in hosts with various memory configurations - 256MB RAM on XO hardware, 1GB on the recommended config, and high-end hosts may have more RAM. Sure, it is doable -- I can do it for you. Pg cannot take all of that memory, but perhaps 15%-20% is a reasonable footprint. The workload for Pg is mainly Moodle and MediaWiki. Ok. One of the key things for the XS is that we should not OOM, and our working set _must not_ end up in swap. And we have several services we have to run, so it's a bit of a tough diet on RAM usage. We gotta sweat every MB :-) You are right. So, please let me know when you need the config files, and also how can I submit those packages to OLPC repository. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Want to package PostgreSQL for OLPC
On Wed, 2008-06-25 at 09:44 -0400, Martin Langhoff wrote: We have compat packages, and all pam-pgsql, etc in that repository. So, using those files won't be a problem. Fantastic! So python-pgsql and php-pgsql are there too? python-psycopg2 is there, but not php-pgsql. The question is: Is php-pgsql already in OLPC package set? If yes, we have compat packages to satisfy dependencies. If not, I can give it a shot. ... So, please let me know when you need the config files, and also how can I submit those packages to OLPC repository. When? Yesterday ;-) - but perhaps there is no need for rebuilding the packages. What I am wondering about is what the best solution is to maintain those alternative configurations long-term. Perhaps we could have a postgresql-server-altinit package that provides an alternative init script + config files and disables the init script from postgresql-server. The alternative init check memory size, and starts with the appropriate config files. Maybe we can solve this issue during initdb process, and copy the preconfigured config file based on the memory to data directory after we run initdb. It may be easier to maintain... BTW... I must admit that I did not work for OLPC project before, so I don't know how to do things. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Want to package PostgreSQL for OLPC
Hi, Per e-mail from Michael Stone: https://www.redhat.com/archives/fedora-devel-list/2008-June/msg01331.html I would like to assist packaging PostgreSQL for OLPC. I'm the upstream packager for PostgreSQL, and I also maintain 30+ packages for Fedora+EPEL. What should I do next? Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Want to package PostgreSQL for OLPC
On Wed, 2008-06-25 at 08:48 -0400, Martin Langhoff wrote: How hard is it to get a backport of Pg8.2/8.3, plus some key dependencies (php-pgsql, python-pgsql, pam-pgsql) recompiled to use the new libpq, all on F7? http://yum.pgsqlrpms.org ;) I have already built all PG combinations against Fedora 7-8-9 and RHEL 4,5. We have compat packages, and all pam-pgsql, etc in that repository. So, using those files won't be a problem. Also - I see you work at CommandPrompt -- so I'll throw a wishlist item I have on my list in your direction. Perhaps you, or someone at CommandPrompt has something similar. With Pg packaged, what we will need to come up with is ~3 sets of config files tuned for different memory footprints. The same XS image will be used in hosts with various memory configurations - 256MB RAM on XO hardware, 1GB on the recommended config, and high-end hosts may have more RAM. Sure, it is doable -- I can do it for you. Pg cannot take all of that memory, but perhaps 15%-20% is a reasonable footprint. The workload for Pg is mainly Moodle and MediaWiki. Ok. One of the key things for the XS is that we should not OOM, and our working set _must not_ end up in swap. And we have several services we have to run, so it's a bit of a tough diet on RAM usage. We gotta sweat every MB :-) You are right. So, please let me know when you need the config files, and also how can I submit those packages to OLPC repository. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Want to package PostgreSQL for OLPC
On Wed, 2008-06-25 at 09:44 -0400, Martin Langhoff wrote: We have compat packages, and all pam-pgsql, etc in that repository. So, using those files won't be a problem. Fantastic! So python-pgsql and php-pgsql are there too? python-psycopg2 is there, but not php-pgsql. The question is: Is php-pgsql already in OLPC package set? If yes, we have compat packages to satisfy dependencies. If not, I can give it a shot. ... So, please let me know when you need the config files, and also how can I submit those packages to OLPC repository. When? Yesterday ;-) - but perhaps there is no need for rebuilding the packages. What I am wondering about is what the best solution is to maintain those alternative configurations long-term. Perhaps we could have a postgresql-server-altinit package that provides an alternative init script + config files and disables the init script from postgresql-server. The alternative init check memory size, and starts with the appropriate config files. Maybe we can solve this issue during initdb process, and copy the preconfigured config file based on the memory to data directory after we run initdb. It may be easier to maintain... BTW... I must admit that I did not work for OLPC project before, so I don't know how to do things. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
