Skip to content

Commit

Permalink
Initial commit for Babelfish 1.x development
Browse files Browse the repository at this point in the history
Signed-off-by: Jim C. Nasby <[email protected]>
  • Loading branch information
nasbyj committed Oct 28, 2021
1 parent e849f3f commit 3e4958b
Show file tree
Hide file tree
Showing 148 changed files with 5,696 additions and 315 deletions.
61 changes: 61 additions & 0 deletions .github/ISSUE_TEMPLATE/bug.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
name: Babelfish for PostgreSQL Bug Report
description: File a bug report
title: "[Bug]: "
labels: ["bug", "triage"]
assignees:
- amazon-auto
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to fill out this bug report!
- type: input
id: contact
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. [email protected]
validations:
required: false
- type: textarea
id: what-happened
attributes:
label: What happened?
description: Also tell us, what did you expect to happen?
placeholder: Tell us what you see!
value: "A bug happened!"
validations:
required: true
- type: dropdown
id: version
attributes:
label: Version
description: What version of our software are you running?
options:
- 13_4 (Default)
validations:
required: true
- type: dropdown
id: os
attributes:
label: What flavour of Linux are you running into the bug?
multiple: true
options:
- Ubuntu (Default)
- Fedora
- Amazon Linux
- Other
- type: textarea
id: logs
attributes:
label: Relevant log output
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: shell
- type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://aws.github.io/code-of-conduct-faq)
options:
- label: I agree to follow this project's Code of Conduct
required: true
5 changes: 5 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
blank_issues_enabled: true
contact_links:
- name: Babelfish for PostgreSQL Website
url: https://github.community/
about: Please ask and answer questions here.
49 changes: 49 additions & 0 deletions .github/ISSUE_TEMPLATE/enhancement.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
name: Babelfish for PostgreSQL Feature Request Form
description: Propose an enhancement for Babelfish for PostgreSQL
title: "[Enhancement]: "
labels: ["enhancement", "untriaged"]
assignees:
- amazon-auto
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to help us improving Babelfish!
- type: input
id: contact
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. [email protected]
validations:
required: false
- type: textarea
id: what-intends
attributes:
label: What this feature/enhancement tries to solve?
description: Be explanatory, as detailed as you can.
placeholder: Tell us what you have in mind!
value: "This is my feature request!"
validations:
required: true
- type: textarea
id: brief-desc-implementation
attributes:
label: If want to provide us a more details about how to implement.
description: Share with us if you have more details about the implementation.
validations:
required: false
- type: textarea
id: docs
attributes:
label: Relevant documentation
description: Please attach relevant documentation.
render: shell
- type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://aws.github.io/code-of-conduct-faq)
options:
- label: I agree to follow this project's Code of Conduct
required: true
42 changes: 42 additions & 0 deletions .github/ISSUE_TEMPLATE/question.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
name: Babelfish for PostgreSQL Question
description: Make a question to maintainers
title: "[Question]: "
labels: ["question", "untriaged"]
assignees:
- amazon-auto
body:
- type: markdown
attributes:
value: |
Thanks for using Babelfish!
- type: input
id: contact
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. [email protected]
validations:
required: false
- type: textarea
id: what-question
attributes:
label: What's the question?
description: Tell us about your doubts.
placeholder: Do your question as detailed as possible.
value: "I have a question!"
validations:
required: true
- type: textarea
id: logs
attributes:
label: Relevant log output or information
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: shell
- type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://aws.github.io/code-of-conduct-faq)
options:
- label: I agree to follow this project's Code of Conduct
required: true
15 changes: 15 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
### Description

[Describe what this change achieves]

### Issues Resolved

[List any issues this PR will resolve]

### Check List

- [ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the PostgreSQL license, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/babelfish-for-postgresql/postgresql_modified_for_babelfish/blob/main/CONTRIBUTING.md#developer-certificate-of-origin).
36 changes: 36 additions & 0 deletions .github/workflows/main.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
name: CI

on:
push:
branches:
- 13_4
pull_request:
branches:
- 13_4

jobs:
build-and-run-tests:
name: Build and run tests
runs-on: ubuntu-latest
steps:
- name: clone-repository
uses: actions/checkout@v2
- name: build-postgres
run: |
./configure
make world-bin -j8
- name: run-tests
run: |
make check -j8
- name: upload-test-summary
if: failure()
uses: actions/upload-artifact@v2
with:
name: regression-summary
path: src/test/regress/regression.out
- name: upload-test-differences
if: failure()
uses: actions/upload-artifact@v2
with:
name: regression-differences
path: src/test/regress/regression.diffs
5 changes: 4 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,9 @@ win32ver.rc
*.exe
lib*dll.def
lib*.pc
*regression.diffs
*regression.out


# Local excludes in root directory
/GNUmakefile
Expand All @@ -41,4 +44,4 @@ lib*.pc
/pgsql.sln.cache
/Debug/
/Release/
/tmp_install/
/tmp_install/
4 changes: 4 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
## Code of Conduct
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
[email protected] with any additional questions or comments.
23 changes: 23 additions & 0 deletions LICENSE.PostgreSQL
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)

Portions Copyright (c) 1996-2021, PostgreSQL Global Development Group

Portions Copyright (c) 1994, The Regents of the University of California

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement
is hereby granted, provided that the above copyright notice and this
paragraph and the following two paragraphs appear in all copies.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS
ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
95 changes: 95 additions & 0 deletions MAINTAINERS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,95 @@
- [Overview](#overview)
- [Current Maintainers](#current-maintainers)
- [Maintainer Responsibilities](#maintainer-responsibilities)
- [Uphold Code of Conduct](#uphold-code-of-conduct)
- [Prioritize Security](#prioritize-security)
- [Review Pull Requests](#review-pull-requests)
- [Triage Open Issues](#triage-open-issues)
- [Be Responsive](#be-responsive)
- [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo)
- [Add Continious Integration Checks](#add-continious-integration-checks)
- [Developer Certificate of Origin Workflow](#developer-certificate-of-origin-workflow)
- [Use Semver](#use-semver)
- [Release Frequently](#release-frequently)
- [Promote Other Maintainers](#promote-other-maintainers)

## Overview

This document explains who the maintainers are (see below), what they do in this repo, and how they should be doing it. If you're interested in contributing, see [CONTRIBUTING](CONTRIBUTING.md).

## Current Maintainers

Initially, GitHub maintainers will be from within AWS: As we progress, we'll add additional external maintainers. Guidelines for adding external maintainers will be published. Current list of maintainers

| Maintainer | GitHub ID | Affiliation |
| ------------------------ | --------------------------------------- | ----------- |
| Zane Li | [zli236](https://github.com/zli236) | Amazon |
| Huansong Fu | [huansong](https://github.com/huansong) | Amazon |
| Kuntal Ghosh | [slightst](https://github.com/slightst) | Amazon |
| Di Wu | [macwoody](https://github.com/macwoody) | Amazon |
| Korry Douglas | [korryd](https://github.com/korryd) | Amazon |
| Suprio Pal | [suprio-amzn](https://github.com/suprio-amzn) | Amazon |
| Jim Mlodgenski | [jim-mlodgenski](https://github.com/jim-mlodgenski) | Amazon |
| Jim Nasby | [nasbyj](https://github.com/nasbyj) | Amazon |
| Jim Finnerty | [JimFinnerty](https://github.com/JimFinnerty) | Amazon |
| Rob VErschoor | [rcv-aws](https://github.com/rcv-aws) | Amazon |
| Simon Lightstone | [slightst](https://github.com/slightst) | Amazon |
| Richard Waymire | [waymire](https://github.com/waymire) | Amazon |
| Gopinath Pai | [gopinathpai](https://github.com/gopinathpai)| Amazon |



## Maintainer Responsibilities

Maintainers are active and visible members of the community, and have [maintain-level permissions on a repository](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization). Use those privileges to serve the community and evolve code as follows.

### Uphold Code of Conduct

Model the behavior set forward by the [Code of Conduct](CODE_OF_CONDUCT.md) and raise any violations to other maintainers and admins.

### Prioritize Security

Security is your number one priority. Maintainer's Github keys must be password protected securely and any reported security vulnerabilities are addressed before features or bugs.

Note that this repository is monitored and supported 24/7 by Amazon Security, see [Reporting a Vulnerability](SECURITY.md) for details.

### Review Pull Requests

Review pull requests regularly, comment, suggest, reject, merge and close. Accept only high quality pull-requests. Provide code reviews and guidance on incomming pull requests. Don't let PRs be stale and do your best to be helpful to contributors.

### Triage Open Issues

Manage labels, review issues regularly, and triage by labelling them.

All repositories in this organization have a standard set of labels, including `bug`, `documentation`, `duplicate`, `enhancement`, `good first issue`, `help wanted`, `blocker`, `invalid`, `question`, `wontfix`, and `untriaged`, along with release labels, such as `v1.0.0`, `v1.1.0`, `v2.0.0`, `patch`, and `backport`.

Use labels to target an issue or a PR for a given release, add `help wanted` to good issues for new community members, and `blocker` for issues that scare you or need immediate attention. Request for more information from a submitter if an issue is not clear. Create new labels as needed by the project.

### Be Responsive

Respond to enhancement requests, and forum posts. Allocate time to reviewing and commenting on issues and conversations as they come in.

### Maintain Overall Health of the Repo

Keep the `main` branch at production quality at all times. Backport features as needed. Cut release branches and tags to enable future patches.

### Add Continious Integration Checks

Add integration checks that validate pull requests and pushes to ease the burden on Pull Request reviewers.

#### Developer Certificate of Origin Workflow

Validates pull requests commits are all signed with the doc, [doc.yml](./workflows/dco.yml).

### Use Semver

Use and enforce [semantic versioning](https://semver.org/) and do not let breaking changes be made outside of major releases.

### Release Frequently

Make frequent project releases to the community.

### Promote Other Maintainers

Assist, add, and remove [MAINTAINERS](MAINTAINERS.md). Exercise good judgement, and propose high quality contributors to become co-maintainers.

22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
## Babelfish for PostgreSQL

This repository contains the PostgreSQL code base with a patch applied to
enable some additional functionality provided by the Babelfish extensions. The
Babelfish community strives to minimize the amount of changes to the PostgreSQL
database engine, and will be working with the PostgreSQL development community
to merge these changes into PostgreSQL where possible.

This repository is available for building patched PostgreSQL binaries. Patches
with the modifications to community PostgreSQL are made available with every
[Babelfish release](https://github.com/babelfish-for-postgresql/babelfish_extensions/releases).

More information on Babelfish for PostgreSQL can be found at
[babelfishpg.org](https://babelfishpg.org)

Changes to community PostgreSQL that are unrelated to Babelfish should be made
through the PostgreSQL community. If you'd like to contribute to Babelfish,
please use [this repo](https://github.com/babelfish-for-postgresql/babelfish_extensions).

Babelfish would not be possible without the work and dedication of the hundreds
of people who have contributed to creation of PostgreSQL itself. Everyone
involved in the development of PostgreSQL has our gratitude.
3 changes: 3 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
## Reporting a Vulnerability

If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [email protected]. Please do **not** create a public GitHub issue.
2 changes: 1 addition & 1 deletion doc/src/sgml/config.sgml
Original file line number Diff line number Diff line change
Expand Up @@ -1825,7 +1825,7 @@ include_dir 'conf.d'
reducing the amount of decoded changes written to disk.
</para>
</listitem>
</varlistentry>
</varlistentry>

<varlistentry id="guc-max-stack-depth" xreflabel="max_stack_depth">
<term><varname>max_stack_depth</varname> (<type>integer</type>)
Expand Down
Loading

0 comments on commit 3e4958b

Please sign in to comment.