|
|
3 天之前 | |
|---|---|---|
| .. | ||
| src | 3 天之前 | |
| README.md | 3 天之前 | |
| benchmark_config.json | 3 天之前 | |
| config.toml | 3 天之前 | |
| docker-compose.yml | 3 天之前 | |
| postgresql.dockerfile | 4 年之前 | |
| postgrest.conf | 3 天之前 | |
| postgrest.dockerfile | 3 天之前 | |
The tests were run with:
http://localhost:3000/rpc/jsonser
http://localhost:3000/rpc/plaintext
http://localhost:3000/rpc/query?queries=
http://localhost:8080/cached_query?queries=
http://localhost:3000/rpc/updates?queries=
Technically, this is implemented (maybe not correctly though). However, the benchmark issues this as a GET request. PostgREST sets the transaction to READ ONLY for GET requests, as they are supposed to be idempotent. Hence this results in an error. Calling the endpoint with POST works though.
http://localhost:3000/rpc/fortunes.html
This is supposed to work, but somehow the benchmark harness doesn't count the queries correctly? Was not able to figure this one out.