Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Pg16 tests #340

Merged
merged 3 commits into from
Aug 24, 2023
Merged

WIP: Pg16 tests #340

merged 3 commits into from
Aug 24, 2023

Conversation

robe2
Copy link
Contributor

@robe2 robe2 commented Aug 13, 2023

The pg16 does not yet have PostGIS, but tests pass.

So I'm labeling this a WIP since I will change to install PostGIS once PostGIS is available in apt.postgresql.org

Note other changes needed to be made for this:

 - Add new postgres16, it's misnamed as moment, cause it doesn't have
   postgis yet
    - Change postgresql_postgis.sh to:

       - Use trusted instead of apt-key which is deprecated
       - Added a condition to postgresql_postgis.sh to skip PostGIS
	 install if no PostGIS version is specified
         Since PostGIS is not yet available in
	 apt.postgresql.org repo for PG16
       - Use pgdg-snapshot instead of main
	 repo except for PG12
	 (it has all stable branches and main)
       - For PG12, jsut continue to use main repo,
         since PostGIS 2.5 is not carried in snapshot
@robe2 robe2 force-pushed the pg16-tests branch 3 times, most recently from 6ecc3e6 to 692e3a3 Compare August 13, 2023 21:31
@pblottiere
Copy link
Member

Hello @robe2,

Thanks a lot for this PR 👍.

Considering that this PR fixes #338 and also add PG16 tests, I propose to:

  1. merge this PR and close the corresponding issue
  2. close Fix for PG16 stringToQualifiedNameList #339
  3. then I'll update the README and the documentation about PG16 CI
  4. I'll update the CI as soon as PostGIS is available in the repository for PG16

What do you think?

@robe2
Copy link
Contributor Author

robe2 commented Aug 20, 2023

Hello @robe2,

Thanks a lot for this PR 👍.

Considering that this PR fixes #338 and also add PG16 tests, I propose to:

1. merge this PR and close the corresponding issue

2. close [Fix for PG16 stringToQualifiedNameList #339](https://github.com/pgpointcloud/pointcloud/pull/339)

3. then I'll update the README and the documentation about PG16 CI

4. I'll update the CI as soon as PostGIS is available in the repository for PG16

What do you think?

Sounds good to me.

@pblottiere pblottiere merged commit ebd5789 into pgpointcloud:master Aug 24, 2023
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants