| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
| Cc: | Sean Utt <sean(at)strateja(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Postgresql Materialized views |
| Date: | 2008-01-14 03:57:48 |
| Message-ID: | 478ADDBC.5070906@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I think, though, that telling them that they must work on a
> certain feature, because that's what the users are asking for, is the
> wrong approach. Not to say that is exactly what you are requesting, but
> I suggest that is where you are leading.
>
> Cheers,
> mark
>
The more communication between users and developers the better.
Companies would pay a fortune for the user complaints, moans and groans,
suggestions, bug reports and demands that postgresql sees in a single day.
IMHO developers need reality checks ... well so do users but for
different reasons. There is no quicker way to kill a product or project
than to ignore the needs/wants of the user/customer base (open-source or
not).
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trevor Talbot | 2008-01-14 03:59:08 | Re: Some notes about the index-functions security vulnerability |
| Previous Message | Mark Mielke | 2008-01-14 02:36:04 | Re: Postgresql Materialized views |