From: | Octavio Alvarez <alvarezp(at)alvarezp(dot)ods(dot)org> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pet Peeves? |
Date: | 2009-01-30 09:23:04 |
Message-ID: | 1233307384.19180.16.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2009-01-29 at 13:16 +0000, Gregory Stark wrote:
> So, what do people say? Is Postgres perfect in your world or does it
> do some
> things which rub you the wrong way?
For me:
Lack of column-level privileges. It just doesn't help scalability at
all. You end up having different tables each with different permissions,
or having to create a view with a ruleset attached, having to update the
view for each definition change in the view.
Lack of allowing subqueries in CHECK constraints and lack of allowing
references to other columns in DEFAULT clauses (like columns that
default to a calculated formula, but may be overridden if it violates a
constraint)
Now, last time I checked, Postgresql lacked an SQL extension to create
crosstab queries. Even though contrib have some helper functions, they
are not official and work only if the number of columns is actually
predefined. For instance if you want to create a query to produce
different paths to go through a graph, being represented by 1 arc per
record, you will never be able to predict the final number of columns
(path steps) needed for the crosstab without doing the whole query one
extra time to get the max(step).
Of course, there are things that PostgreSQL does great, like the
user-defined types.
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2009-01-30 11:05:20 | Re: Pet Peeves? |
Previous Message | Ivan Sergio Borgonovo | 2009-01-30 08:50:59 | Re: ssl to more than one server |