Re: Planning incompatibilities for Postgres 10.0

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Planning incompatibilities for Postgres 10.0
Date: 2013-05-28 17:13:44
Message-ID: 51A4E5C8.1050503@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 05/28/2013 08:36 AM, Hannu Krosing wrote:

>> The conversation does not change.
>>
>> Further, we are not Firefox. We are not user software. We are
>> developer software.
> At least some of the real-world problems with PostgreSQL
> comes from "We are developer software" mentality.
>
> Yes, We are developer software, but we are also a
> DBA/maintainer/infrastructure manager

I would not hire any of those three that weren't smart enough to
understand our versioning scheme or had the wits to open a web browser
and google:

PostgreSQL versioning

The answer is link #1 on Google.

That said, I won't raise a stink. I am not really of a strong opinion
either way except to say we are not solving a problem. We are just
tickling each other's fancies.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-05-28 17:48:02 Re: XLogInsert scaling, revisited
Previous Message Clark C. Evans 2013-05-28 17:00:51 GRANT role_name TO role_name ON database_name