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

Where should hypopg be installed? #19

Open
pgiraud opened this issue Dec 19, 2024 · 3 comments
Open

Where should hypopg be installed? #19

pgiraud opened this issue Dec 19, 2024 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@pgiraud
Copy link
Member

pgiraud commented Dec 19, 2024

In the SQL script where extensions are installed, hypopg is installed in the postgres and in template1. Is there any reason for that?

In the powa-web interface, hypopg is marked as not installed.

Screenshot from 2024-12-19 18-55-33

@rjuju rjuju self-assigned this Dec 19, 2024
@rjuju rjuju added the question Further information is requested label Dec 19, 2024
@rjuju
Copy link
Member

rjuju commented Dec 19, 2024

hypopg is installed in the postgres and in template1. Is there any reason for that?

yes, it's to ensure that hypopg is installed in a new database by default. It's also in postgres in case people use this database rather than creating a new database.

In the powa-web interface, hypopg is marked as not installed.

Yes, because I assumed that no one is going to use this image to try to optimize powa-archivist itself (something like powa-team/powa-archivist@18d0b0c for instance). And if someone wants to do having to install an extension is not going to be the hard part of the process.

@pgiraud
Copy link
Member Author

pgiraud commented Dec 20, 2024

yes, it's to ensure that hypopg is installed in a new database by default. It's also in postgres in case people use this database rather than creating a new database.

I understand. I don't know why by I got a case (with the powa-dev-demo.yml compose file) where I got a database where hypopg extension was not created. Weird.

Yes, because I assumed that no one is going to use this image to try to optimize powa-archivist itself (something like powa-team/powa-archivist@18d0b0c for instance). And if someone wants to do having to install an extension is not going to be the hard part of the process.

As far as I understand, the table in configuration shows the extensions installed in the powa database.
https://github.com/powa-team/powa-web/blob/master/powa/config.py#L480

In 4.2.2, the extensions was marked as installed even if it was not installed in powa database.
Screenshot from 2024-12-20 08-37-09
Screenshot obtained running powa-web 4.2.2 and powa-archivist-15:4.2.2 image.

@rjuju
Copy link
Member

rjuju commented Dec 20, 2024

I don't know why by I got a case (with the powa-dev-demo.yml compose file) where I got a database where hypopg extension was not created.

maybe the database was created before the hypopg part? if you have the full logs I could see if I see anything, otherwise you could look at the xmin of the various rows to try to infer what happened first.

As far as I understand, the table in configuration shows the extensions installed in the powa database.
https://github.com/powa-team/powa-web/blob/master/powa/config.py#L480

In 4.2.2, the extensions was marked as installed even if it was not installed in powa database.

yes I entirely overhauled the configuration page because it was quite misleading. there are now different sections based on the extension type. maybe a new section for "support extension" or something like that would be good, but we would need to connect to all databases to show the full information and that can be problematic. so maybe not showing the per database status, or showing it on another per database page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants