Sync Greengage 6.30.0 changes

.abi-check/6.29.1_arenadata68/postgres.symbols.ignore

@@ -0,0 +1 @@
+ConfigureNamesBool_gp

.github/CODE_OF_CONDUCT.md

@@ -1,50 +1,45 @@
-# Code of Conduct
+# Greengage DB Community Code of Conduct
 
-## Intro
+Greengage DB is an open community project. Every Greengage DB user or developer is responsible for making the community a place where people want to come back. We expect all community members to maintain professional ethics and communicate respectfully and politely.
 
-Standing on the shoulders of the giants means not only leveraging the code base of the most successful open source relational database (PostgreSQL) but also taking a page out of one of the most successful open source governance bodies: Apache Software Foundation (ASF). Greengage Database developer community has adopted not only the Apache License but also the following code of conduct heavily borrowing from an ASF’s:
+## Community Development Principles
 
-This code of conduct applies to all spaces that are associated with the participation in the Greengage Database open source project, including chat, all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. A code of conduct which is specific to in-person events (ie., conferences, meetups, etc.) is expected to be a superset of this document covering additional principles put forward by the organizers of the event(s) and landlords of the space where the event is held.
+In developing code, documentation, and any other products of intellectual work, we are guided by principles that are important for the development of the community.
 
-We expect this code of conduct to be honored by everyone who participates in the Greengage Database community formally or informally, or claims any affiliation with the project, in any activities and especially when representing the Greengage Database project, in any role.
+**Collaboration**
 
-This code is not exhaustive or complete. It serves to distil our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter so that it can enrich all of us and the technical communities in which we participate.
+Anyone can join the Greengage DB community and make a contribution.
 
-## Specific guidelines
+**Equality**
 
-We strive to:
-1. **Be open** We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.
-2. **Be empathetic**, welcoming, friendly, and patient. We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. We should be respectful when dealing with other community members as well as with people outside our community.
-3. **Be collaborative**. Our work will be used by other people, and in turn will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
-4. **Be inquisitive**. Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving Greengage Database project code.
-5. **Be careful in the words that we choose**. Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:
-    * Violent threats or language directed against another person.
-    * Sexist, racist, or otherwise discriminatory jokes and language.
-    * Posting sexually explicit or violent material.
-    * Posting (or threatening to post) other people's personally identifying information ("doxing").
-    * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
-    * Personal insults, especially those using racist or sexist terms.
-    * Unwelcome sexual attention.
-    * Excessive or unnecessary profanity.
-    * Repeated harassment of others. In general, if someone asks you to stop, then stop.
-    * Advocating for, or encouraging, any of the above behaviour.
-6. **Be concise**. Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.
-    Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.
-     Try to stay on topic, especially in discussions that are already fairly large.
-7. **Step down considerately**. Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.
+The contribution of each community member will be assessed equally, based on its objective significance for the project.
 
-## Diversity statement
+**Opportunities**
 
-Greengage Database project welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining. Although we may not be able to satisfy everyone, we will always work to treat everyone well.
+Community members who contribute to Greengage DB can influence the direction of the product's development.
 
-No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability.
+**Availability**
 
-Though we welcome people fluent in all languages, Greengage Database project development is conducted in English.
+The project code will be distributed under an open license for community members anywhere in the world.
 
-Standards for behaviour in this community are detailed in the Code of Conduct above. We expect participants in our community to meet these standards in all their interactions and to help others to do so as well.
+## Code of Conduct in Action
 
-## Reporting guidelines
+This code of conduct applies to all available channels of interaction between community members, including comments on code or documentation, the project's social media, and online and offline events that are partially or fully dedicated to Greengage DB.
 
-While this code of conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful.
+Every member of the Greengage DB community is expected to adhere to the project’s code of conduct, especially when speaking on behalf of Greengage DB in the public space.
+We encourage everyone to be interested in Greengage DB, regardless of their track record or formal qualifications. This does not negate the important procedures for code and documentation quality, but it does require respectful and polite treatment.
 
-If you believe someone is violating this code of conduct, you may reply to them and point out this code of conduct. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your compliance issues in confidence to coc@greengagedb.org. This will go to an individual who is entrusted with your report.
+The Greengage DB project exists thanks to the voluntary contributions of its members. Some of them may leave the project over time, and this decision should be respected in the same way as their initial involvement. We expect this code of conduct to be followed in the event of parting with the project, and the departing community member is supposed to treat those who remain with respect.
+
+## Appropriate Conduct
+
+No personal characteristics can serve as grounds for refusing to work for the benefit of the Greengage DB project or belittling your contribution to it. This code of conduct considers any attacks on a person unacceptable. These are the basic principles of communication in the community.
+
+Unacceptable behavior is any threat to use violence, damage social or professional reputation, expressed to an individual or a group of people. Threats to damage the Greengage DB project or its reputation or the implementation of such threats are also a violation of this code of conduct. Harassment of any kind and violation of the basic principles of communication are not tolerated in the Greengage DB community.
+
+In the event of receiving a warning about inappropriate behavior, it is necessary to immediately stop it. Subsequent violations of the Code of Conduct will serve as grounds for taking restrictive measures against the violator, up to and including exclusion from the community.
+
+## Reporting
+
+In many cases, simply sending a link to this code of conduct will be enough to maintain a good community culture. If you see a discussion where the code may potentially be violated, proactively send a link to it.
+In some cases, violations may require issuing warnings and other restrictive measures. In this case, please contact us at **code@greengagedb.org**.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,84 @@
+name: Bug Report
+description: Create a report to help us improve GreengageDB
+title: "[Bug] "
+labels: ["bug"]
+assignees: []
+
+body:
+ - type: textarea
+   id: problem_description
+   attributes:
+    label: "Describe the problem"
+    description: "Please describe the issue you observed, and any steps we can take to reproduce it"
+    placeholder: "Describe the problem you encountered..."
+   validations:
+    required: true
+
+ - type: textarea
+   id: reproduction_steps
+   attributes:
+    label: "How to reproduce"
+    description: "Steps to reproduce the behavior"
+    placeholder: |
+     1. 
+     2. 
+     3. 
+     ...
+   validations:
+    required: true
+
+ - type: textarea
+   id: expected_behavior
+   attributes:
+    label: "Expected behavior"
+    description: "A clear and concise description of what you expected to happen"
+    placeholder: "Describe what you expected to happen..."
+   validations:
+    required: true
+
+ - type: textarea
+   id: additional_data
+   attributes:
+    label: "Additional data"
+    description: |
+     If the problem is SQL-related, include a copy of the SQL query and the schema.
+
+     If a segment in your cluster encountered a fatal error, supply the contents of the log directory (at minimum of the affected segment(s), but preferably all segments).
+
+     Note that log files can contain confidential information.
+    placeholder: |
+     SQL Query:
+     Schema:
+     Log files:
+     ...
+
+ - type: input
+   id: environment_greengagedb
+   attributes:
+    label: "GreengageDB version"
+    description: "What version of GreengageDB are you using?"
+   validations:
+    required: true
+
+ - type: input
+   id: environment_os
+   attributes:
+    label: "Server OS"
+    description: "What operating system is the server running on?"
+    placeholder: "e.g. Linux/Distrib version"
+   validations:
+    required: true
+
+ - type: input
+   id: environment_client
+   attributes:
+    label: "Client application"
+    description: "What client application are you using?"
+    placeholder: "e.g. psql, JDBC, pxf, ..."
+
+ - type: textarea
+   id: additional_context
+   attributes:
+    label: "Additional context"
+    description: "What was the impact? Add any other context about the problem here"
+    placeholder: "Add any other relevant context about the problem..."

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for Greengage project
+title: "[Feature]"
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. 
+
+**Describe the solution**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context about the feature request, user stories or examples of usage.

.github/workflows/README.md

@@ -37,6 +37,82 @@ operating systems:
   DockerHub. Runs for push to `main` (retags to `latest`) and tags (uses tag
   like `6.28.2`) after build.
 
+## Release Workflow
+
+A separate workflow `Greengage release` handles the uploading of Debian package
+to GitHub releases. It is triggered when a release is published and uses a
+composite action to manage package deployment.
+
+### Key Features
+
+- **Triggers:** `release: [published]` - Runs when a release is published,
+including re-publishing.
+- **Concurrency:** Uses the same concurrency group as the CI workflow
+(`Greengage CI-${{ github.ref }}`) to ensure proper sequencing and prevent race
+conditions.
+- **Cache-based Artifacts:** Restores built packages from cache using the
+commit SHA as the key, rather than downloading artifacts from previous jobs.
+- **Manual Recovery:** If the cache is missing, the workflow checks the status
+of the last build for the tag and provides clear instructions for manual
+intervention. It does not automatically trigger builds to avoid infinite loops.
+- **Safe Uploads:** Uploads packages with fixed naming patterns and optional
+overwrite (`clobber` flag).
+
+### Behavior
+
+1. **Normal Flow (Cache Available):** Restores packages from cache, renames
+them to the pattern `${PACKAGE_NAME}${VERSION}.${EXT}`, and uploads to the
+release.
+2. **Cache Miss Scenarios:**
+   - **No previous build or previous build successful:** Provides instructions
+   to manually trigger the CI build, then restart the release workflow.
+   - **Previous build failed:** Reports the failure with a link to the failed
+   run and requires manual fixing before retrying.
+
+The release workflow is designed to be robust and provide clear feedback when
+issues occur, ensuring that releases are always consistent and reliable.
+
+## SQL Dump Workflow
+
+A separate workflow `Greengage SQL Dump` is responsible for generating SQL dump
+artifacts after the main CI process completes successfully. It is triggered
+automatically upon the completion of the `Greengage CI` workflow.
+
+### Key Features
+
+- **Triggers:** `workflow_run: workflows: ["Greengage CI"], types: [completed]`
+- **Branch Targeting:** Runs only for the `main` and `7.x` branches.
+- **Version Detection:** Automatically determines the database version (6 or 7)
+based on the triggering branch.
+- **Artifact Creation:** Executes regression tests with the `dump_db: "true"`
+parameter to generate a SQL dump archive, which is then uploaded as a workflow
+artifact.
+- **Controlled Execution:** Since the main CI workflow runs on `main` and `7.x`
+branches only for push events (which occur after final merge of a PR), SQL dump
+are generated exclusively for verified, approved patches after they are merged
+into the main branches.
+- **Artifact Retention:** The generated SQL dump artifact is retained 90 days
+after the last download. Each new run of the `behave tests gpexpand` workflow
+(which consumes this artifact as a consumer) resets this retention period to
+90 days when it downloads the artifact.
+
+### Behavior
+
+1. **Triggering:** Automatically starts after the `Greengage CI` workflow
+finishes on the `main` or `7.x` branch.
+2. **Preparation:** Configures Docker storage on the runner to utilize
+`/mnt/docker` for increased disk space.
+3. **Version Mapping:** Maps the branch name (`main` -> version 6, `7.x` ->
+version 7) to select the correct Docker image for testing.
+4. **Dump Generation:** Runs the regression test suite using the reusable
+action with the `dump_db` option enabled, which creates a
+`*_postgres_sqldump.tar` file.
+5. **Artifact Upload:** Uploads the generated SQL dump archive as a named
+artifact (e.g., `sqldump_ggdb7_ubuntu`) to the workflow run.
+
+This workflow ensures that a current database schema dump is available as an
+artifact following successful CI runs on the primary branches `main` and `7.x`.
+
 ## Configuration
 
 The workflow is parameterized to support flexibility:

.github/workflows/greengage-abi-tests.yml

@@ -8,22 +8,7 @@ concurrency:
 on:
   workflow_dispatch:
   pull_request:
-    paths:
-      - 'concourse/scripts/**'
-      - 'src/**'
-      - '.github/workflows/**'
-      - '.github/scripts/**'
-      - '.abi-check/**'
-
-  push:
-    branches:
-      - 6X_STABLE
-    paths:
-      - 'concourse/scripts/**'
-      - 'src/**'
-      - '.github/workflows/**'
-      - '.github/scripts/**'
-      - '.abi-check/**'
+    branches: ['**']
 
 env:
   # workaround required for checkout@v3, https://github.com/actions/checkout/issues/1590
@@ -95,8 +80,9 @@ jobs:
       - name: Install dependencies and abi-dumper
         run: |
           sudo gpdb_src/README.ubuntu.bash
-          sudo apt install -y libuv1-dev libpam0g-dev libldap-dev libipc-run-perl abi-dumper
+          sudo apt install -y libuv1-dev libpam0g-dev libldap-dev libipc-run-perl abi-dumper python-pip
           sudo ln -fs python2 /usr/bin/python
+          sudo python -m pip install future
 
       - name: Build Greengage
         run: |