Re: PG vs MySQL
От | Mike Nolan |
---|---|
Тема | Re: PG vs MySQL |
Дата | |
Msg-id | 200403290445.i2T4jODk005619@gw.tssi.com обсуждение исходный текст |
Ответ на | Re: PG vs MySQL ("Marc G. Fournier" <scrappy@postgresql.org>) |
Ответы |
Re: PG vs MySQL
Re: PG vs MySQL |
Список | pgsql-general |
> Just curious ... restricting \l itself isn't too difficult ... but how > does MySQL restrict the ability to do something like: > > SELECT datname FROM pg_database; > > or does it not have an equivalent to that? I'm not much of an expert in MySQL, but on my ISP 'show databases' only shows MY databases. I find MySQL's security tables arcane and confusing, but it may be that I'm just more familiar with the way PG does it, because from the traffic on the pgsql-general list it seems like questions about how to set up the pg_hba.conf and pg_ident.conf are commonplace. I also wonder how well the pg_hba.conf method will scale. What happens if there are hundreds of client databases or thousands of entries in pg_hba.conf? -- Mike Nolan
В списке pgsql-general по дате отправления: