On Wed, Jan 16, 2019 at 01:12:15PM -0500, Greg Troxel wrote:
> John Nemeth <jnem...@cue.bc.ca> writes:
>
> > } If it turns out your data size or query/update rate is too much, I would
> > } use postgres. I know you said you don't want a process, but unlike
> > } mysql postgres is really easy to set up.
> >
> > It would be nice to get rid of some of the FUD around here.
> > MySQL is quite simple to setup, especially if you're installing it
> > from pkgsrc. mysql-cluster is complex to setup, but that is for
> > master-master replication with redundancy. The regular mysql-server
> > is just pkgin mysql-server, set the "root" password and you're off
> > to the races.
>
> That wasn't my experience. WIth pgsql, I was able to just 'createuser'
> the username matching the one the daemon that wants to use it. With
> mysql, there was a bunch of stuff about creating username/password pairs
> and for a particular db-using application, it was a lot more work to get
> things to actually run correctly. My memory, which could be off, is
> that I also had to configure it not to listen beyond localhost.
>
> But, the pkgsrc package was indeed first class, and things were only
> annoying at the 30-minute level.
The "problem" with pgsql is that, in a default install, any user
can access locally any database just putting the name of the user
as an argument to the client psql(1) without needing to know a
password (by default, you can switch to a pgsql privileged user
just knowing his name).
I guess that MySQL being used a lot with websites has, by default, to
require more strict connection (password) procedures. This probably
explains that (I do not use MySQL but slightly PostgreSQL---and nothing
(no server) when possible...)
FWIW
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
