Version detection

[laurenceisla]

We need to find a way on how to detect the PostgREST version. Maybe using this PostgREST/postgrest#2647 could help, but if it fails it needs to be retrieved from another source.

https://github.com/laurenceisla/postgrest-openapi/blob/74430c6e72fdf745a63727020679101a50c4fd6d/src/postgrest.sql#L506-L511

[steve-chavez]

Hm, what's the need for the version?

[laurenceisla]

@steve-chavez For the Info Object it's mostly to get the same result as the core repo. But it may be also needed to generate the documentarion URL (although this one needs a simplified version).

Edit: Btw I mistakenly said "PostgreSQL" version instead of "PostgREST" version.

[steve-chavez]

Got it. So I guess the same problem exists for the server_proxy_uri too:

postgrest-openapi/sql/main.sql

Lines 3 to 6 in 106e51c

	create or replace function get_postgrest_openapi_spec(
	schemas text[],
	server_proxy_uri text default 'http://0.0.0.0:3000',
	version text default null

While the schemas can be obtained from our tx-settings.

---

Maybe we need a concept of session-scoped settings on PostgREST to make this work. So each config option (coming from file or env var) gets a set_config($,$, false) thus is always available. Unlike tx-settings this wouldn't have a perf cost impact.

[wayland]

What are tx-settings? I'm assuming it means transaction settings? Is this set_config within a transaction or something?

[steve-chavez]

I'm assuming it means transaction settings? Is this set_config within a transaction or something?

@wayland Yes, basically set_config(.., .., true). We use them like mentioned on PostgREST/postgrest#3019