This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
| > for i in 'age' 'apache_datasketches' 'cstore_fdw' 'jsonb_deep_sum' 'override' 'overrideDerivation' 'periods' 'pg_auto_failover' 'pg_bigm' 'pg_cron' 'pg_ed25519' 'pg_hint_plan' 'pg_hll' 'pg_ivm' 'pg_net' 'pg_partman' 'pg_rational' 'pg_relusage' 'pg_repack' 'pg_safeupdate' 'pg_similarity' 'pg_topn' 'pgaudit' 'pgjwt' 'pgroonga' 'pgrouting' 'pgsql-http' 'pgtap' 'pgvector' 'pipelinedb' 'plpgsql_check' 'plr' 'plv8' 'postgis' 'promscale_extension' 'recurseForDerivations' 'repmgr' 'rum' 'smlar' 'tds_fdw' 'temporal_tables' 'timescaledb' 'timescaledb-apache' 'timescaledb_toolkit' 'tsearch_extras' 'wal2json'; do | |
| nix build -L "n#postgresql15Packages.${i}" && print -l -- "\nBuilt ${i} (15)\n" | |
| nix build -L "n#postgresql16Packages.${i}" && print -l -- "\nBuilt ${i} (16)\n" | |
| done | |
| error: | |
| … in the condition of the assert statement | |
| at /nix/store/i6hq63805y784dml4j8pgkrz3lryxzld-source/lib/customisation.nix:222:17: | |
| 221| in commonAttrs // { |
| services: | |
| jwks-updater: | |
| image: jwks-updater | |
| build: | |
| context: . | |
| dockerfile: ./jwks-updater.Dockerfile | |
| depends_on: | |
| postgres: # Disable this if you are using an external Postgres database | |
| condition: service_healthy | |
| postgrest: |
The idea is to improve the SQL language, specifically the join syntax, for the special but common case when joining on foreign key columns.
Example below taken from PostgreSQL documentation [1]
In SQL-89, we didn't have any JOIN syntax yet, so queries were written in this way:
The background to this is explained in https://gist.github.com/wolfgangwalther/5425d64e7b0d20aad71f6f68474d9f19 This explains the algorithm to transform a pg_node_tree to a JSON format, that can be used by PostgREST to obtain the :targetList of the view.
Author: Wolfgang Walther https://github.com/wolfgangwalther
License: MIT
| filename='yourfilename' | |
| filetype='text/csv' | |
| token='my oauth token' | |
| url='http://localhost/upload' | |
| curl "$url" \ | |
| --form "data=@$filename;type=$filetype" \ | |
| --form "name=somename" \ | |
| -H "Authorization: Bearer $token" | |
There a times when you need to build something from the nix unstable channel. For example the master contains a new package you need, but the next nixpkgs release is somewhere in the future, and you need this package now. In this guide I want to show how to install packages from unstable by using nix-env. Furthermore I hope to give a basic understanding of the channels concept.
A channel is a set of expressions which includes severall build, installation and configuration instructions for packages, services and the system itself. The repository normaly used here is nixpkgs. It is developed at https://github.com/NixOS/nixpkgs.
The unstable channel is a copy of the NixOS/nixpkgs master. It is pulled from github once in a while and will be available from a mirror under https://nixos.org/channels/nixpkgs-unstable. Since NixOS uses half-anual released stable channels, some changes (especially new f
