[Klug-general] kentlug.org down?

[MacGyveR]

On Monday 14 December 2009, Karl Buckland wrote:
> Yes, both MySQL and PHP use more memory than they probably should, but
> then it's not like memory is particularly expensive? PHP allows rapid
> development of software, which usually runs pretty fast, but there is
> a memory overhead for that. Dan: Is some PHP caching software
> installed, like APC Cache?
>
> Having developed and administered PHP/MySQL/Postgres websites, I
> personally prefer MySQL over postgres. Not only is MySQL faster, but
> Postgres is not as well documented, takes more configuration and seems
> to leave more things to the developer that I would expect to 'just
> work'. Perhaps if you're happy to learn about the shifting internals
> of Postgres you can get a better result than MySQL, but that doesn't
> make it the easier tool to develop with.
>
> As for losing data with MySQL - that's never happened to me either and
> is something people seem to throw around from their experiences of
> MySQL from 5+ years ago? Besides - you do back up, right?
>
> Karl
>
> 2009/12/14 J D Freeman <klug at quixotic.org.uk>:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Mon, Dec 14, 2009 at 01:47:12PM +0000, Peter Childs wrote:
> >> Did I not remember you saying at a meeting ages ago, to avoid MySql if
> >> at all possible as it was a memory hog and to use PostgreSQL if
> >> possible? Or maybe a was dreaming (it was a while ago now)
> >
> > I said to avoid mysql if atall possible. I also said it was a memory hog.
> > The relationship of the two statements (do one because of the other), was
> > not mentioned. Personally I would have used postgres, or none atall, but
> > I didn't setup the drupal setup.
> >
> >> Anyway I would never trust any data to MySQL because I can be sure of
> >> losing it sooner or later. (I say I can because I'm sure it must work
> >> fine for someone else who I'm not sure)
> >
> > There are many fine reasons for avoiding mysql, many. I personally avoid
> > it at all possible opportunities, I don't like it's attemps at
> > clustering.
> >
> > Ultimately, by far the most important thing, the fluffy elephant mascot
> > of postgres is so damn cute :p
> >
> > J
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (GNU/Linux)
> >
> > iD8DBQFLJly142M0lILkmGIRAsaqAJ9od22IDBn7/DlJLFQh/3Vnvhql5QCgqnnK
> > zMFfGr0C5pQqTOJrvb3ptjU=
> > =hvzu
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > Kent mailing list
> > Kent at mailman.lug.org.uk
> > https://mailman.lug.org.uk/mailman/listinfo/kent
>
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent

Do we really need to use mysql or postgresal on the server, wouldn't sqlite 
work just as well for our small needs?