-
Couldn't load subscription status.
- Fork 8
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: timescale/pgspot
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.9.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: timescale/pgspot
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.9.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 13 commits
- 19 files changed
- 2 contributors
Commits on Jan 6, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 3185d96 - Browse repository at this point
Copy the full SHA 3185d96View commit details
Commits on Jan 31, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 83b8b24 - Browse repository at this point
Copy the full SHA 83b8b24View commit details
Commits on Feb 2, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 1a3af6a - Browse repository at this point
Copy the full SHA 1a3af6aView commit details
Commits on Feb 8, 2025
-
Check for misquoted arguments to SET search_path
When using SET search_path the schemas must not be enclosed in single quotes as otherwise the list of schemas will be treated as a single schema name instead. Erroneous example: ``` SET search_path TO 'pg_catalog, temp'; ``` Setting the search_path this way will result in the actual search_path being pg_temp, pg_catalog, "pg_catalog, pg_temp" instead of the intended value of pg_catalog, pg_temp. This would allow shadowing catalog relations with relations in the pg_temp schema.
Configuration menu - View commit details
-
Copy full SHA for 9b0837d - Browse repository at this point
Copy the full SHA 9b0837dView commit details
Commits on Mar 1, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 3589601 - Browse repository at this point
Copy the full SHA 3589601View commit details
Commits on Apr 3, 2025
-
Configuration menu - View commit details
-
Copy full SHA for b8ebfa3 - Browse repository at this point
Copy the full SHA b8ebfa3View commit details
Commits on Apr 6, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 742bf95 - Browse repository at this point
Copy the full SHA 742bf95View commit details
Commits on Apr 19, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 0fcfc5b - Browse repository at this point
Copy the full SHA 0fcfc5bView commit details
Commits on May 8, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 544ff90 - Browse repository at this point
Copy the full SHA 544ff90View commit details
Commits on May 18, 2025
-
Configuration menu - View commit details
-
Copy full SHA for d1d4312 - Browse repository at this point
Copy the full SHA d1d4312View commit details -
Configuration menu - View commit details
-
Copy full SHA for 213d2d8 - Browse repository at this point
Copy the full SHA 213d2d8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 35d55d4 - Browse repository at this point
Copy the full SHA 35d55d4View commit details -
Configuration menu - View commit details
-
Copy full SHA for a8b9df7 - Browse repository at this point
Copy the full SHA a8b9df7View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.9.0...0.9.1