Re: PostgreSQL 11 Press Release Feedback

"Jonathan S. Katz" <[email protected]> Thu, 23 Aug 2018 00:09:47 -0400
Newsgroups gmane.comp.db.postgresql.advocacy
Message-ID <[email protected]>
Hi Amit,

> On Aug 22, 2018, at 9:12 PM, Amit Langote <[email protected]> wrote:
> 
> Hi Jonathan,
> 
> Thanks for working on this.
> 
> On 2018/08/23 0:40, Jonathan S. Katz wrote:
>> Hi,
>> 
>> As we have recently released PostgreSQL 11 Beta 3, the time to releasing
>> PostgreSQL 11 is drawing near. I wanted to share with you a draft of the
>> proposed press release to solicit *constructive* feedback, specifically looking
>> for:
>> 
>> - Grammatical mistakes / typos / awkward + unclear language
>> - Technical inaccuracies
>> - Suggestions for missing features that should be highlighted
>> - Quotes - you can see there are lots of room for them ;-)
>> 
>> Please bear in mind that the release is targeted towards the users of
>> PostgreSQL, the vast majority of whom do not post to the mailing lists, and the
>> principle idea behind the language is to help clearly explain why one should
>> upgrade, if not use, PostgreSQL 11 and how to utilize the new features
>> available. For many people, this is their only viewpoint into whats in the
>> release, so let's make sure it makes them excited about using PostgreSQL!
>> 
>> If you wish to provide feedback, please send it no later than Aug 31, 2018.
>> After that, the draft will need to be finalized (barring changes from -hackers
>> on which features are included).
>> 
>> If you wish to provide a quote, please send an
>> email to [email protected] with your name, organization, and the quote.
>> 
>> Below is a copy of the press release draft:
> 
> About the following:
> 
> "PostgreSQL 11 also supports partitioned tables that utilize the
> PostgreSQL foreign data wrapper,
> [postgres_fdw](https://www.postgresql.org/docs/current/static/postgres-fdw.html <https://www.postgresql.org/docs/current/static/postgres-fdw.html>),
> enabling users to combine partitioning with data federation techniques."
> 
> Just to clarify, we support partitioned tables containing partitions that
> utilize FDWs even in PostgreSQL 10 [1].  Although, they were not handled
> by tuple routing, so offered limited functionality as partitions.
> PostgreSQL 11 fixed that limitation, which makes them more useful.

Thanks for the clarification! Would something like “PostgreSQL 11 _provides better
support for_…” work better?

Jonathan
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE+oS2la8r95ogZD/x8QSccp8cZScFAlt+M4sACgkQ8QSccp8c
ZSfSXA/9Fl3g71LKjPyrZtSiZ0QTO2rvOcVuNIPGcJtNDIVmEVAWH+ACLN1LcqbA
V6aAWQgpn2hRYJnNoBfiRRfTSaRt4Kzjmv/UyYktC34k9WoSt232s28VUlGk6AI4
XFmfRLNI3FIzjQui9znrSyhcKOd7RNmbtqaixBlyewNDznzPR28uASlByECzI11d
0zqOfsLPPnI6H1UxACB63iZq1FItdxuwFZ7bZ8JnIkycaH1EWg1KTn7KcEWU3ytB
hwbcdoAwq5q5VksdH/LhyW3VELY0qgexfao/T1GGmfvFPBSV4p0AiKuk0podf8jL
KGmWUii95pnh+N2vRQFtfS/2lQxbionvuof9EcYjYTJtlQQUyIbzOKSgNc9nQO+/
ls2WJiRRLIzevNLQwTeu56CROe2t7elCVX2gptYC6OsZTD3BwPKZlgsvQ81d51JQ
xyPj7MvDFvrzTP3r8SuNSqwd17YevGMsjGc+iezizQT8tdVG8W9rb0MxtvOquVYw
K46pqlu7dJjt/dVifGb1B0eLRRBLAEu3ws0H62vZCUoVb4zbG/d6YqU4HxQ5UBto
T1MZw1/Hes+Pop0y0C4v292AhmDiDDiMneTGxcBgfuMRJJ8jxRGRJDcz2KJnn8vq
rT/HB4ortXcQAM5BIFxbJIcdqRaNJxoa+kcFe+I30hhDN9WwEyc=
=Qhda
-----END PGP SIGNATURE-----