Re: [HACKERS] One of our own begins a new life
On Fri, 2006-09-15 at 09:38 -0700, Joshua D. Drake wrote: Hello, Hi Joshua, Yeah, this is a cross post and it is slightly off topic but IMHO this is important. Tomorrow one of our own, Devrim Gunduz is becoming a man. He is sucking it up, and committing to the cvs repo of project marriage. May the patches reviewers be kind to him! Congratz Devrim, have a good honey moon and we look forward to having you back in a couple of weeks! I have done a quick post-commit review of his recent patch, it looked (very) good to me :) I'd also like to raise the point of how good he's on pretending to be a belly dancer. -- Enver signature.asc Description: This is a digitally signed message part
Re: [Pgsqlrpms-hackers] [HACKERS] Safer auto-initdb for RPM initscript
Merhaba, On Fri, Aug 25, 2006 at 10:30:56AM -0400, Andrew Dunstan wrote: It is extremely careful. The point is that the NFS mount will hide the existing datadir from initdb. Am I the only one who believes that PostgreSQL project is not supposed to fix (or include workarounds for) some other systems that actually don't work very well? If NFS is causing trouble, let it be. Thanks, -- Enver signature.asc Description: Digital signature
Re: [HACKERS] Transaction Speed
Hi, On Thu, Jul 20, 2006 at 02:36:53PM +0200, moises wrote: For example Inserts, Update, delete, etc. If you need a storage for structured data, database servers are good to go. If you need a very fast flow of not-so-needed and okay-to-miss-we-can-regenerate type of data storage you can go with in-memory storage such as memcache[1] or PostgreSQL's temporary table[2] feature. I think the latter would slightly perform better. Enjoy, [1] http://www.danga.com/memcached/ [2] http://www.postgresql.org/docs/8.1/static/sql-createtable.html -- Enver ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] pgNixInstaller: Making PostgreSQL relocatable
Hi, We have been having a short talk with Devrim this evening about the pgnixInstaller[1] project he started[2] a while ago. I have briefly read over the thread following the project announce, particularly comments on issues about package systems of distributions and integration with them. I believe the project will add some value to the PostgreSQL community, so I'd like to join and add my grain of salt. Main goal of the project appears to be making installation and configuration of PostgreSQL server a no-brainer, not easier. Any moron you can get to the /mouse/[3] should be able to get PostgreSQL up and running in some short time period. And that moron should be able to do it in some fashion that's not so good, but the installation should work. Fortunately we're not alone in the universe, several other projects suffered from the very same problem. Including the much larger OpenOffice.org project. I think some of you have installed it on your favorite Unix-alike OS using it's click-click-and-go installer, when distributions did not have packages of it -- ancient times. We'll be doing that for PostgreSQL, I think it's a fantastic way for me to get involved. In order to achieve this *properly*, I intend to make PostgreSQL relocatable, that is, PostgreSQL should be able to run if you `copy` it's binaries somewhere else -- no matter where you `./configure --prefix`ed it. I took a very quick look at some parts of the codebase and it seems doable to me. Apparently we'll be avoiding package systems integration and development-packages-requirement issues mentioned in the thread. Next step would be a simple, possibly shell-script and xdialog/zenity[4] based prototype installer. I personally can't afford the Python thing, Solaris and possibly others don't have it yet and embedding Python in a shell script is not the brightest idea obviously. Now the question, would you accept patches for this, or are we going to maintain some set of patches? May you have suggestions about any other direction, I'd be more than happy to know. Cheers, [1] http://pgfoundry.org/projects/pgnixinstaller/ [2] http://archives.postgresql.org/pgsql-hackers/2006-01/msg00943.php [3] http://www.joelonsoftware.com/articles/fog24.html -- Enver ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] pgNixInstaller: Making PostgreSQL relocatable
Hey, Enver ALTIN wrote: Next step would be a simple, possibly shell-script and xdialog/zenity[4] based prototype installer. I personally can't afford the Python thing, Solaris and possibly others don't have it yet and embedding Python in a shell script is not the brightest idea obviously. [4] http://cvs.gnome.org/viewcvs/zenity/ :) -- Enver ---(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: [HACKERS] pgNixInstaller: Making PostgreSQL relocatable
Hi Tom, Tom Lane wrote: Enver ALTIN [EMAIL PROTECTED] writes: In order to achieve this *properly*, I intend to make PostgreSQL relocatable, that is, PostgreSQL should be able to run if you `copy` it's binaries somewhere else -- no matter where you `./configure --prefix`ed it. I took a very quick look at some parts of the codebase and it seems doable to me. s/doable/already done/, no? I did a Google search on relocatable PostgreSQL and the first result[1] said it's already done. Apparently it didn't work for me on Solaris 8 (linking problems). I'll be looking at it sometime today. Thanks for your immediate response :) [1] http://www.postgresql.org/docs/faqs.TODO.html -- Enver ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
