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

PostgreSQL 13 support #246

Closed
devrimgunduz opened this issue Sep 24, 2020 · 10 comments
Closed

PostgreSQL 13 support #246

devrimgunduz opened this issue Sep 24, 2020 · 10 comments

Comments

@devrimgunduz
Copy link

Hi,

PostgreSQL 13.0 will be out today. When will you release a v13 compatible version?

Regards, Devrim

@devrimgunduz
Copy link
Author

Hi,

Ping.

@dvarrazzo
Copy link
Member

Hello,

I'll try to wrap a release in a few days.

If anyone is able to finish existing MR that'd be great.

@dvarrazzo
Copy link
Member

Released.

@dvarrazzo
Copy link
Member

Hi @devrimgunduz

For some time we have had problems testing Postgres 9.6 on Travis: ubuntu packages seem broken, see https://www.postgresql.org/message-id/CA%2Bmi_8a1oEnCzkt0CvqysgY4MQ6jEefjmS%3Dq_K-AvOx%3DF7m2%2BQ%40mail.gmail.com

I understand you are mostly responsible of the RPM, right? Do you know who is the authority for deb packages to report this issue? I reported it to pgsql-bugs but I don't think the core devs are the right recipients.

Thank you very much!

@devrimgunduz
Copy link
Author

Hi @dvarrazzo ,

@df7cb is deb guru.

Cheers, Devrim

@df7cb
Copy link
Contributor

df7cb commented Oct 1, 2020

Travis is doing things I don't know with their PG installation, like modifying /etc/init.d/postgresql to refuse starting more than one instance. What works for me is purging everything and then installing PG in the desired version.

The /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh script has switches to allow that: https://github.com/df7cb/pg_dirtyread/blob/master/.travis.yml#L20-L25

@dvarrazzo
Copy link
Member

Thank you @df7cb I'll take a look at your script to see if we can make ours more robust.

So do you think the fact that pg 9.6 installation behaves differently from e.g. 9.5 and 10 is something to blame on Travis and there is no slightly different dependency in the debs?

@df7cb
Copy link
Contributor

df7cb commented Oct 1, 2020

9.6 isn't different in any way that would come to mind now. PG10+ has the difference that the -contrib package is gone and was merged into the main package, but that's likely not relevant here. I just retriggered one of my travis jobs that didn't use the "purge and reinstall" strategy yet, but that worked on all versions as well (and incidentally, it's also on xenial).

Fwiw, exactly for the purpose of testing extensions I extended the support of old PG versions on apt.pg.o all the way back to ancient 8.2, so you can drop your "Dinosaur" archive and still move testing to some modern distribution.

# Dinosaur package kindly provided by psycopg

@dvarrazzo
Copy link
Member

@df7cb ok, that's weird; I'll try using your suggested script and strategy to get 9.6 running again.

Thank you for your dinosaurs replacement packages! However I took advantage of this release to drop support for PG < 9.4, so they aren't used any more in this project. They might be useful for other projects though (psycopg, pgmp...)

@MichaelDBA
Copy link
Collaborator

Why support EOL'd versions of Postgres?

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

No branches or pull requests

4 participants