Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Avoid automatic minor version upgrades of PostgreSQL during image builds #186

Copy link
Copy link
Closed
@fcanovai

Description

@fcanovai
Issue body actions

In #93 there was a misalignment between the declared minor and the actual pg version installed in the container. This was caused by the container release happening after the pgdg package release, with our rebuild happening in between.

PostgreSQL 16.2 was out on 2024-02-08. The postgresql community image was out on 2024-02-12. pgvector 0.6.0 was packaged on 2024-02-09, with the following dependencies on bullseye:

Depends: postgresql-16, postgresql-16-jit-llvm (>= 13), libc6 (>= 2.14)

However, that dependency wasn't satisfied by postgresql-16.1

Version: 16.1-1.pgdg110+1
Provides: postgresql-16-jit-llvm (= 11), postgresql-contrib-16

And 16.2 was already available, so it upgraded.

This can happen on every minor upgrade. We should prevent unwanted minor upgrades.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.