Thread: Is v7.1 stable enough?
Hello, Not so long ago the feasibility of using PostgreSQL for archiving mail and news articles was discussed (briefly). I am planning to put the database to work for just that purpose on a web-based e-mail site (switching from MySQL whose table locking on INSERT becomes a performance bottleneck). To work around the 8 KB page limit, I would have to use the 7.1 beta version, though, or store messages in files and reference those files from the database. The latter solution does not really appeal to me, as it makes ensuring referential integrity a pain. My question is: how stable is the current 7.1 code? Can it be used in a production environment or is it meant for internal bug squashing only? Am I asking for problems? Thanks for your advice - JPL
Jan Ploski <jpljpl@gmx.de> writes: > My question is: how stable is the current 7.1 code? Can it be used > in a production environment or is it meant for internal bug > squashing only? Am I asking for problems? I've found it to be very stable, though I'm not banging hard on it. The developers are taling about an RC1 release quite soon. -Doug
I would have a look on balsa which is a gnome mail client that use mysql for storing e-mails. May be it could be converted to PG. Franck Martin Network and Database Development Officer SOPAC South Pacific Applied Geoscience Commission Fiji E-mail: franck@sopac.org <mailto:franck@sopac.org> Web site: http://www.sopac.org/ <http://www.sopac.org/> Support FMaps: http://fmaps.sourceforge.net/ <http://fmaps.sourceforge.net/> This e-mail is intended for its addresses only. Do not forward this e-mail without approval. The views expressed in this e-mail may not be necessarily the views of SOPAC. -----Original Message----- From: Jan Ploski [mailto:jpljpl@gmx.de] Sent: Wednesday, 14 March 2001 3:21 To: pgsql-general@postgresql.org Subject: [GENERAL] Is v7.1 stable enough? Hello, Not so long ago the feasibility of using PostgreSQL for archiving mail and news articles was discussed (briefly). I am planning to put the database to work for just that purpose on a web-based e-mail site (switching from MySQL whose table locking on INSERT becomes a performance bottleneck). To work around the 8 KB page limit, I would have to use the 7.1 beta version, though, or store messages in files and reference those files from the database. The latter solution does not really appeal to me, as it makes ensuring referential integrity a pain. My question is: how stable is the current 7.1 code? Can it be used in a production environment or is it meant for internal bug squashing only? Am I asking for problems? Thanks for your advice - JPL ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
Jan Ploski <jpljpl@gmx.de> writes:
> how stable is the current 7.1 code? Can it be used in a production
> environment or is it meant for internal bug squashing only? Am I
> asking for problems?
You want an honest opinion? I'd say 7.1 is on the cusp: it's probably
stable enough for production use, but there are probably a few bugs left
too. If you're willing to run regular backups and report/help track
down bugs, then go for it. If you want to leave the work to other
people, then go away and come back in a few months.
Note that we have just been making some changes in the WAL log format.
You can save yourself some upgrade trouble if you use a snapshot dated
after today --- or perhaps safer, wait for the next formal beta release.
regards, tom lane
> Not so long ago the feasibility of using PostgreSQL for archiving mail > and news articles was discussed (briefly). I am planning to put the > database to work for just that purpose on a web-based e-mail site > (switching from MySQL whose table locking on INSERT becomes a > performance bottleneck). To work around the 8 KB page limit, I would > have to use the 7.1 beta version, though, or store messages in files and > reference those files from the database. The latter solution does not > really appeal to me, as it makes ensuring referential integrity a pain. > My question is: how stable is the current 7.1 code? Can it be used in a > production environment > or is it meant for internal bug squashing only? Am I asking for > problems? I do not think so, because I have been playing with it and have found that 7.1 works fine. The new features are a real boon and blessing. Admittedly I have only been using it to develop a relatively simple web application for which the database is only tiny biggest table is only ~300 tuples - I am not using any esoteric features either, just selects, inserts, updates and a couple of plsql functions all called from php. Also it is all single user at the moment ( there is only one of me ) and the query rate is very low. Updated using cvsup a couple or three days ago. I'd go for it if I was in your position. -- Sincerely etc., NAME Christopher Sawtell CELL PHONE 021 257 4451 ICQ UIN 45863470 EMAIL csawtell @ xtra . co . nz CNOTES ftp://ftp.funet.fi/pub/languages/C/tutorials/sawtell_C.tar.gz -->> Please refrain from using HTML or WORD attachments in e-mails to me <<--