Hi all,
only want to link this blog post
http://blog.kimiensoftware.com/2011/04/top-10-missing-postgresql-features , i
think he may have any good points.
Miguel Angel.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.post
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Linos
> Sent: Monday, April 25, 2011 2:42 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] 10 missing features
>
> Hi all,
>
On Mon, Apr 25, 2011 at 08:29:43AM -0600, mark wrote:
> One or two of his points are on my list as well, but as far as a TOP 10
> missing features that PG "needs" his probably aren't anywhere close to what
> the majority of people are in need of.
When I had to hire Postgres DBAs, I hated hiring p
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of mark
Sent: Monday, April 25, 2011 10:30 AM
To: 'Linos'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] 10 missing features
> -Original Messag
On 04/25/2011 10:48 AM, Andrew Sullivan wrote:
You can see this in certain items in the top 10. Three, four, five,
seven, maybe 8 eight, and ten all seemed to me to be things I've
actually done before, but not using something directly inside
Postgres.
The idea that something must ship in th
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Greg Smith
> Sent: Monday, April 25, 2011 4:23 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] 10 missing features
>
> On 04/
On 04/25/2011 04:54 PM, Nicholson, Brad (Toronto, ON, CA) wrote:
The problem is that there is a lot of noise in the add-on space. There
are lots of things out there that are no longer supported or partially
supported. There is a fairly high barrier of entry into figuring out
which tools to use,
On Tue, Apr 26, 2011 at 06:21:21AM -0400, Greg Smith wrote:
> addressed doesn't start with "how can PostgreSQL duplicate the
> Oracle solution to this problem", which is how many of these
> incoming requests for features start. The alternate question of
> "how do you provide something with the sa
On Monday 25 April 2011 10:41:36 Linos wrote:
> Hi all,
> only want to link this blog post
> http://blog.kimiensoftware.com/2011/04/top-10-missing-postgresql-features ,
> i think he may have any good points.
>
>
> Miguel Angel.
Maybe the best point is the one between the lines: That Postgr
On Tue, 26 Apr 2011 14:30:19 +0200, Leif Biberg Kristensen wrote:
On Monday 25 April 2011 10:41:36 Linos wrote:
Hi all,
only want to link this blog post
http://blog.kimiensoftware.com/2011/04/top-10-missing-postgresql-features
,
i think he may have any good points.
Miguel Angel.
M
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Radoslaw Smogura
> Sent: Tuesday, April 26, 2011 9:55 AM
> To: Leif Biberg Kristensen
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL
On Mon, Apr 25, 2011 at 3:41 AM, Linos wrote:
> Hi all,
> only want to link this blog post
> http://blog.kimiensoftware.com/2011/04/top-10-missing-postgresql-features ,
> i think he may have any good points.
my take:
1. Query progress
Seen a couple of near miss proposals -- good feature,
On Tue, Apr 26, 2011 at 5:39 AM, Andrew Sullivan wrote:
> In commercial development, this is where product development managers
> live. They identify the meaning of the feature request, and then
> identify how the actual need (rather than the requested feature) can
> be addressed.
But there are
13 matches
Mail list logo