Postgresql -- initial impressions and comments - Mailing list pgsql-general
From | j.random.programmer |
---|---|
Subject | Postgresql -- initial impressions and comments |
Date | |
Msg-id | 20021203024403.86529.qmail@web14208.mail.yahoo.com Whole thread Raw |
Responses |
Re: Postgresql -- initial impressions and comments
Re: Postgresql -- initial impressions and comments Re: Postgresql -- initial impressions and comments |
List | pgsql-general |
Hi: I am a long time MySQL/Innodb user. I just installed postgres 7.3 on my linux box and thought I'd post some comments: 1) Running postgres as non-root is understandable but should not be _mandated_ (for totally private networks, it's overkill). Trust the user... 2) It's not clear what md5 password auth does. (a) Is the password stored as md5 in the database itself, or only md5's on the wire (from client to server) and then thereafter stored as plain text in the db itself ? (b) If the client is responsible for the md5 encryption, then does the JDBC driver do this for us automatically ? (c) Is there a md5 function in the database ? The docs don't really answer these points at all - especially (b) and (c). 3) The documentation needs to be radically improved. The mysql docs are much more comprehensive. Postgres wins hands down in the database internals documentation (mysql doesn't have any) but loses in the userland documentation. 4) The auto-increment ("serial") fields are very badly documented. Normally, I want to say something like: INSERT into foo values (null, 'a', 'b',...) where the first field is defined as serial. However I can't send null to that field and expect it to be auto incremented - I have to either list out my fields in the statment (and omit the serial field): INSERT into foo (field_a, field_b,...) values ('a', 'b', ...) which is a drag or I have to use a funky nextval command. Why can't postgres simply accept null for the serial field and simply fill in the next value ? This would make it easier to use (don't have to type in the field list) and more consistent (with mysql and perhaps other databases). 5) There is no way to grant permissions on all tables within a database to some user. You have to grant permissions on each table one-by-one. What I want to do (and mysql allows this) is something like: GRANT ALL on foodb.* to user_bar; where 'foodb' is the name of a database. This sucks. 6) Well, docs again: there are no examples or techniques for importing/exporting comma or tab delimited files from/to tables ? Is this possible but I just didn't find it ? Well, having played with postgres for the first time, these were the initial (after 4-5 hours) points that came up. But overall, it looks and feels like a solid product. The hot dump is a nice feature - I can dump the db without shutting it down - innodb in contrast charges $$ for this feature. Best regards, javadesigner@yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
pgsql-general by date: