Re: ALTER TABLESPACE MOVE command tag tweak - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ALTER TABLESPACE MOVE command tag tweak
Date
Msg-id CA+TgmobA5cO_7k907TSyegGkBupxJrTiMGbkdov721P3Hx5zVg@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLESPACE MOVE command tag tweak  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER TABLESPACE MOVE command tag tweak
List pgsql-hackers
On Thu, Aug 14, 2014 at 6:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: pgbench --tuple-size option
Next
From: Antonin Houska
Date:
Subject: Another logical decoding assertion failure