From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLESPACE MOVE command tag tweak |
Date: | 2014-08-15 12:46:30 |
Message-ID: | CA+TgmobA5cO_7k907TSyegGkBupxJrTiMGbkdov721P3Hx5zVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 14, 2014 at 6:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> We really should not be making changes of this type less than a month
>> from our ostensible release date. That is not enough time for us to
>> notice if the changes turn out to be not as good as we think they are.
>
> If it weren't for the fact that we'll be wedded forevermore to a bad
> choice of syntax, I might agree with you. But at this point, the
> alternatives we have are to fix it now, or fix it never. I don't
> like #2.
Or postpone the release for another month or two. There's still a few
other unresolved issues, too, like the problems with psql and expanded
mode; and the JSONB toast problems. The latter is relatively new, but
we don't have a proposed patch for it yet unless there's on in an
email I haven't read yet, and the former has been lingering for many
months without getting appreciably closer to a resolution.
I like releasing in September as much as anyone, but that contemplates
people taking care to get known issues fixed before the second half of
August.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Antonin Houska | 2014-08-15 12:53:45 | Another logical decoding assertion failure |
Previous Message | Fujii Masao | 2014-08-15 12:42:54 | Re: pgbench --tuple-size option |