aboutsummaryrefslogtreecommitdiff
path: root/sqitch/sqitch.plan
Commit message (Collapse)AuthorAge
* Partition the package_derivations_by_guix_revision_range tableChristopher Baines2022-05-23
| | | | | | | | | | | | And create a proper git_branches table in the process. I'm hoping this will help with slow deletions from the package_derivations_by_guix_revision_range table in the case where there are lots of branches, since it'll separate the data for one branch from another. These migrations will remove the existing data, so rebuild-package-derivations-table will currently need manually running to regenerate it.
* Add an index on derivation_output_details.idChristopher Baines2021-07-11
| | | | | Where hash is not null, since this helps with the fixed output package derivations query.
* Track package replacementsChristopher Baines2021-07-11
| | | | | | Start at least looking for package replacements, and storing the details (particularly the derivation). I'm looking at doing this so that build servers using the Guix Data Service can build these derivations.
* Add index for package_metadataCanan Talayhan2021-05-27
| | | | | | This index speeds up inserting new entries to the package_metadata table. Signed-off-by: Christopher Baines <mail@cbaines.net>
* Add some indexesChristopher Baines2021-05-17
| | | | This is from reading the slow query log on data.guix.gnu.org.
* Create a table for systemsChristopher Baines2021-04-23
| | | | | | | | And use it for the systems in the derivations and package derivations tables. The primary motivation here is to allow quickly working out what systems the database contains, and having a small table with just the right data seems a good way to do that.
* Store channel instance derivations in a separate transactionChristopher Baines2021-02-02
| | | | | | This means that these derivations are stored, even if a later part of the process fails. Having the channel instance derivations stored might help work out why the failure occurred, or better display information about it.
* Increase statistics targets for the derivation_inputs tableChristopher Baines2020-12-27
| | | | | | It has a lot of rows, and this seems to help the query planning for select-required-builds-that-failed, as I think it helps PostgreSQL better estimate the row counts that different parts of the query will produce.
* Add index to speed up deleting revisionsChristopher Baines2020-10-27
| | | | This is necessary to quickly delete entries from package_derivaitons.
* Regenerate the latest_build_status tableChristopher Baines2020-10-21
| | | | | As it doesn't handle wierdness for statuses, like builds being canceled with a timestamp of 0.
* Add a latest_build_status tableChristopher Baines2020-10-13
| | | | | This will avoid many queries trying to figure out what the latest build status is, which will hopefuly simplify queries as well as improving performance.
* Support storing whether to authenticate commits by git repositoryChristopher Baines2020-10-07
| | | | To allow using the Guix Data Service when commits aren't authenticated.
* Add an index for derivation_sources.derivation_source_file_idChristopher Baines2020-10-02
| | | | As this speeds up deleting derivation_source_files.
* Change a constraint to add ON DELETE CASCADEChristopher Baines2020-10-02
| | | | | | I've not used these in many places, to try and avoid hiding deleting data, but in this case, this will allow more easily deleting the derivation source file nars, by just deleting the derivation_source_files table entry.
* Change the autovacuum config for some tablesChristopher Baines2020-10-01
| | | | | | Looking at data for the the patches deployment of the Guix Data Service, these tables look like they might benefit from vacuuming/analyzing more often, so adjust the configuration so this will hopefully happen.
* Change the locale codeset representationChristopher Baines2020-09-26
| | | | | | | | | | | From the normalized one, to the one actually contained within glibc. Recent versions of glibc also contain symlinks linking the normalized codeset to the locales with the .UTF-8 ending, but older ones do not. Maybe handling codeset normalisation for queries would be good, but the locale values ending in .UTF-8 are more compatible and allow the code to be simplified. For querying, maybe there should be a locales table which handles different representations.
* Change a package_descriptions index to use MD5 of the descriptionChristopher Baines2020-08-23
| | | | | | | | | | To avoid the index data being too large. This was first seen in guix commit 1bb4fd64b7bbe5a17eda6f0ca8105283c038f7c8: psql-query-error (fatal-error PGRES_FATAL_ERROR ERROR: index row size 2808 exceeds maximum 2712 for index "package_descriptions_locale_description_key" HINT: Values larger than 1/3 of a buffer page cannot be indexed.
* Add the package_metadata_tsvectors tableDanjela Lura2020-08-12
| | | | Signed-off-by: Christopher Baines <mail@cbaines.net>
* Add a index to derivation_output_details_setsChristopher Baines2020-07-04
| | | | | | | | This helps with queries like: SELECT * FROM derivation_output_details_sets WHERE ARRAY[5563227] <@ derivation_output_details_ids;
* Remove the constraint on having one derivation build per serverChristopher Baines2020-07-01
| | | | As the Guix Build Coordinator can build one derivation many times.
* Avoid duplicate build status entriesChristopher Baines2020-07-01
| | | | This effectively makes adding build status entries idempotent to some degree.
* Support storing the id's representing builds in other servicesChristopher Baines2020-06-27
| | | | | | | Like Cuirass, or the Guix Data Service. This isn't so necessary with Cuirass, as the derivation/output are unique identifiers, but for the Guix Build Coordinator, one derivation/output can be built many times, with potentially differing results.
* Make build_status.timestamp nullableChristopher Baines2020-06-27
| | | | | | The Guix Build Coordinator doesn't record timestamps for events currently. This is something to fix, but allow for build statuses without timestamps as they're not necessary.
* Get the translated package synopsis and descriptions into the databaseDanjela Lura2020-06-19
| | | | Signed-off-by: Christopher Baines <mail@cbaines.net>
* Get the translated lint checker descriptions into the databaseDanjela Lura2020-06-07
| | | | Signed-off-by: Christopher Baines <mail@cbaines.net>
* Make nar_urls file sizes optionalChristopher Baines2020-06-03
|
* Add a lookup_builds field to the build_servers tableChristopher Baines2020-05-24
| | | | | This is to allow for build servers where only the substitutes should be queried, and it shouldn't be assumed that they're running Cuirass.
* Remove odd package derivations with mismatched systemsChristopher Baines2020-04-24
| | | | | This follows on from 79993bfaeff3097d37838bc0636fc20c6fc4283d, disassociating the relevant derivations from the revisions.
* Make jobs unique by commitChristopher Baines2020-03-28
| | | | | Given that a commit, regardless of what repository it comes from should contain the same exactly the same data, just track jobs by commit.
* Create an index on narinfo_fetch_recordsChristopher Baines2020-03-25
| | | | This greatly improves the performance of the derivation-outputs page.
* Stop using package_versions_by_guix_revision_rangeChristopher Baines2020-03-24
| | | | It's been replaced by the package_derivations_by_guix_revision_range table.
* Generate and store system test derivations for all supported systemsChristopher Baines2020-03-20
| | | | | | | Rather than just the native system. I'm not quite sure of the value here, as I guess system tests should behave the same regardless of the way the software is compiled, but this seems like it could be useful, and being explicit about the system the derivation is for is good.
* Make a constraint deferrableChristopher Baines2020-02-16
| | | | To allow for deferring it in a transaction when deleting derivations.
* Update the build_servers_build_config valuesChristopher Baines2020-02-13
| | | | | Change target to '' if it matches system, as this matches the updated way of storing derivations.
* Start storing channel instance derivationsChristopher Baines2020-02-11
| | | | These are the ones that relate to Guix pull.
* Support excluding and including branches from a repositoryChristopher Baines2020-02-08
| | | | | So that you can have the Guix Data Service only pay attention to some of the branches.
* Rework cross derivations supportChristopher Baines2020-02-08
| | | | | | | | | | | | | | Stop using the system values as targets, and remove package derivation entries where this is the case. Switch the non-cross derivation case to have a target of "", rather than matching the system, as this makes more sense, and is more consistent now that the target values no longer match the system values. Hardcode some more correct target values, and use these instead. Hopefully this can be better integrated with Guix in the future. This commit also includes a migration attempting to shrink some indexes.
* Store information about system testsChristopher Baines2020-02-03
|
* Don't hardcode the expected x-git-repo header valueChristopher Baines2020-01-11
| | | | | Rather than expecting it always to be "guix", store the expected value in the database, and use the value of the header to find the relevant repository.
* Add a table to configure which build servers build whatChristopher Baines2020-01-05
|
* Create an index on the hash component of the store pathChristopher Baines2019-12-29
| | | | For derivation_source_files.
* Add a new table to nars for derivation source filesChristopher Baines2019-12-28
| | | | This will allow serving the nars for derivation source files.
* Create an index for the hash component of derivation filenamesChristopher Baines2019-12-26
| | | | | | This is to aid rendering of narinfo files. They're requested with the path /HASH.narinfo, so to quickly find the relevant derivation, this index can be used.
* Add new derivation_output_details_set_id column to the builds tableChristopher Baines2019-12-12
| | | | | As this will hopefully provide a faster way of associating derivations with builds.
* Start storing and identifying sets of derivation outputsChristopher Baines2019-12-12
| | | | | | | | | | | Derivations are effectively equivalent if they produce the same set of outputs, which is possible because of the equivalence of fixed output derivations. A fixed output derivation can be different, but equivalent, because it produces the same fixed output. To better allow tracking equivalent derivations, primarily to allow working out what derivations might correspond to a build, store the sets of derivation outputs, and which derivations they relate to.
* Add some database indexesChristopher Baines2019-12-12
|
* Deduplicate builds and add a unique indexChristopher Baines2019-12-12
| | | | | | | Duplicate builds could creep in if the code to create them ran concurrently. I didn't exclude them initially, as I was unsure if there should be such a restriction, but at least for now, Cuirass builds map exactly to a single derivation, so use the same restriction here.
* Change nar_urls size to bigintChristopher Baines2019-12-12
| | | | As some nars can be bigger than the size of an int.
* Change nars size to bigintChristopher Baines2019-12-12
| | | | As some nars can be bigger than the maximum size of an int.
* Add a table to record where narinfo files were fetched fromChristopher Baines2019-12-12
| | | | Otherwise it's hard to associated narinfo files to build servers.
generated by cgit v1.2.3 (git 2.45.0) at 2024-11-24 23:08:44 +0000