S3 Select Blog last commit

[raymondyin]

The S3 Select blog for PXF is completed for now.

Please remove the draft: true tag on line 14 in content/post/s3select.md and merge it to master if everyone think it's good to be published.

Thank you very much to you all. It's been a pleasure and privilege working with you.

[cunnie]

Hey @raymondyin ,

Kudos on writing a blog post—I've read the raw Markdown, and here are some notes:

• Please squash your git history — you have 21 commits, they can be squashed to one. The commits titled "Update content/post/s3select", for example, add little value. You'll need to do a git push -f on your branch once you've finished rebasing. Once you're on the master branch (once your commit is merged), don't rebase—it's considered poor form to rewrite history on the master branch.
• "upto" should be rewritten "up to"
• I'd rewrite the following paragraph:

• This naive approach is resource intensive. It will require a lot more CPU time for GPDB to filter unwanted results, and increase network bandwidth to fetch the entire data set just to be thrown away by the filter.
• This naive approach is resource-intensive, requiring significantly more CPU time for GPDB to filter unwanted results and greater network bandwidth to fetch the entire data set (only to be later discarded by the filter).

Good luck & good job!

[frankgh]

@cunnie Raymond was our intern for the summer, and he completed his internship last Friday. I went ahead and squashed everything into a single commit. I also addressed your suggestions. We'll merge this PR next week.