First commit, moving from monorepo

.cargo/config.toml

@@ -0,0 +1,9 @@
+# Global settings - optimize for the native CPU for all targets. This
+# is required by the 'datafusion` crate for maximum performance, and
+# applies in addition to the target-specific settings below
+[build]
+rustflags = ["-Ctarget-cpu=native"]
+
+# PostgreSQL symbols won't be available until runtime
+[target.'cfg(target_os="macos")']
+rustflags = ["-Clink-arg=-Wl,-undefined,dynamic_lookup"]

.gitignore

@@ -0,0 +1,34 @@
+# VS Code
+.vscode/
+
+# macOS
+.DS_Store
+
+# Cargo
+Cargo.lock
+target/
+
+# Rustfmt
+*.rs.bk
+
+# Code Coverage
+*.profraw
+
+# Logs
+*.txt
+*.log
+
+# Benchmarks
+*.csv
+*.csv.gz
+*.tbl
+*.tsv
+*.tsv.gz
+*.zip
+__MACOSX/
+TPC-H_V*/
+
+# Tests
+regression.*
+results/
+.env

CODE_OF_CONDUCT.md

@@ -0,0 +1,127 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available [here](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the
+[FAQ](https://www.contributor-covenant.org/faq). Translations are available
+[here](https://www.contributor-covenant.org/translations).

CONTRIBUTING.md

@@ -0,0 +1,63 @@
+# **Contributing to ParadeDB**
+
+Welcome! We're excited that you're interested in contributing to ParadeDB and want
+to make the process as smooth as possible.
+
+## Technical Info
+
+Before submitting a pull request, please review this document, which outlines what
+conventions to follow when submitting changes. If you have any questions not covered
+in this document, please reach out to us in the [ParadeDB Community Slack](https://join.slack.com/t/paradedbcommunity/shared_invite/zt-217mordsh-ielS6BiZf7VW3rqKBFgAlQ)
+or via [email]([email protected]).
+
+### Development Workflow
+
+ParadeDB is structured as a monorepo containing all the projects, PostgreSQL extension(s), and other
+tools which together make ParadeDB. For development instructions regarding a specific project or Postgres extension,
+please refer to the README in the project's subfolder. For developing ParadeDB itself as the combination
+of all its subprojects, please see below.
+
+All development of ParadeDB is done via Docker and Compose. Our Docker setup is split into three:
+
+- The `docker-compose.dev.yml` file builds our `Dockerfile`, the ParadeDB production image with all its features and extensions enabled. It is used to develop and test ParadeDB Postgres extensions and features as part of the full ParadeDB image. It is also used to develop and test new features and extensions outside of those actively developed by ParadeDB (for instance, installing a new third-party open-source PostgreSQL extension). We recommend using it when developing new features beyond the ParadeDB extensions and subprojects.
+
+- The `docker-compose.yml` file pulls the latest published ParadeDB image from DockerHub. It is used for hobby production deployments. We recommend using it to deploy ParadeDB in your own infrastructure.
+
+### Pull Request Worfklow
+
+All changes to ParadeDB happen through Github Pull Requests. Here is the recommended
+flow for making a change:
+
+1. Before working on a change, please check to see if there is already a GitHub
+   issue open for that change.
+2. If there is not, please open an issue first. This gives the community visibility
+   into what you're working on and allows others to make suggestions and leave comments.
+3. Fork the ParadeDB repo and branch out from the `dev` branch.
+4. Install pre-commit hooks within your fork with `pre-commit install`, to ensure code quality and consistency with upstream.
+5. Make your changes. If you've added new functionality, please add tests.
+6. Open a pull request towards the `dev` branch. Ensure that all tests and checks
+   pass. Note that the ParadeDB repository has pull request title linting in place
+   and follows the [Conventional Commits spec](https://github.com/amannn/action-semantic-pull-request).
+7. Congratulations! Our team will review your pull request.
+
+### Documentation
+
+ParadeDB's public-facing documentation is stored in the `docs` folder. If you are
+adding a new feature that requires new documentation, please open a separate pull
+request containing changes to the documentation only. Once your main pull request
+is merged, the ParadeDB team will review and eventually merge your documentation
+changes as well.
+
+## Legal Info
+
+### Contributor License Agreement
+
+In order for us, Retake, Inc. (dba ParadeDB) to accept patches and other contributions from you, you need to adopt our ParadeDB Contributor License Agreement (the "**CLA**"). The current version of the CLA can be found [here](https://cla-assistant.io/paradedb/paradedb).
+
+ParadeDB uses a tool called CLA Assistant to help us keep track of the CLA status of contributors. CLA Assistant will post a comment to your pull request, indicating whether you have signed the CLA or not. If you have not signed the CLA, you will need to do so before we can accept your contribution. Signing the CLA is a one-time process, is valid for all future contributions to ParadeDB, and can be done in under a minute by signing in with your GitHub account.
+
+If you have any questions about the CLA, please reach out to us in the [ParadeDB Community Slack](https://join.slack.com/t/paradedbcommunity/shared_invite/zt-217mordsh-ielS6BiZf7VW3rqKBFgAlQ) or via email at [[email protected]](mailto:[email protected]).
+
+### License
+
+By contributing to ParadeDB, you agree that your contributions will be licensed under the [GNU Affero General Public License v3.0](LICENSE).

Cargo.toml

@@ -0,0 +1,70 @@
+[package]
+name = "pg_analytics"
+description = "Real-time analytics for PostgreSQL using columnar storage and vectorized execution"
+version = "0.6.2"
+edition = "2021"
+license = "AGPL-3.0"
+
+[lib]
+crate-type = ["cdylib", "rlib"]
+
+[[bin]]
+name = "pgrx_embed_pg_analytics"
+path = "./src/bin/pgrx_embed.rs"
+
+[features]
+default = ["pg16"]
+pg12 = ["pgrx/pg12", "pgrx-tests/pg12" ]
+pg13 = ["pgrx/pg13", "pgrx-tests/pg13" ]
+pg14 = ["pgrx/pg14", "pgrx-tests/pg14" ]
+pg15 = ["pgrx/pg15", "pgrx-tests/pg15" ]
+pg16 = ["pgrx/pg16", "pgrx-tests/pg16" ]
+pg_test = []
+
+[dependencies]
+pgrx = { git = "https://github.com/pgcentralfoundation/pgrx.git", rev = "bef7ab7" }
+serde = "1.0.193"
+serde_json = "1.0.107"
+async-std = { version = "1.12.0", features = ["tokio1"] }
+async-trait = "0.1.77"
+chrono = "0.4.34"
+deltalake = { git = "https://github.com/paradedb/delta-rs.git", features = ["datafusion"] }
+thiserror = "1.0.56"
+indexmap = "2.2.2"
+once_cell = "1.19.0"
+datafusion-federation = { git = "https://github.com/datafusion-contrib/datafusion-federation.git" }
+datafusion-federation-sql = { git = "https://github.com/datafusion-contrib/datafusion-federation.git" }
+futures = "0.3.30"
+regex = "1.10.3"
+memoffset = "0.9.0"
+zstd-sys = "=2.0.9"
+walkdir = "2.5.0"
+url = "2.5.0"
+lazy_static = "1.4.0"
+uuid = "1.8.0"
+
+[dev-dependencies]
+anyhow = "1.0.79"
+approx = "0.5.1"
+async-std = { version = "1.12.0", features = ["attributes"] }
+bigdecimal = { version = "0.3.0", features = ["serde"] }
+bytes = "1.5.0"
+futures-util = "0.3.30"
+pgrx-tests = { git = "https://github.com/pgcentralfoundation/pgrx.git", rev = "bef7ab7" }
+pretty_assertions = "1.4.0"
+rstest = "0.18.2"
+soa_derive = { version = "0.13.0" }
+sqlx = { version = "0.7.3", features = ["postgres", "runtime-async-std", "time", "bigdecimal", "uuid"] }
+time = "0.3.32"
+
+[package.metadata.pgrx]
+pg_sys_includes = ["pg_query_parse.h", "pg_plan.h"]
+
+[profile.dev]
+panic = "unwind"
+
+[profile.release]
+lto = "fat"
+panic = "unwind"
+opt-level = 3
+codegen-units = 1