Add missing docs for release 12.2.0

[laurenceisla]

Adds missing docs for new logging features.

[wolfgangwalther]

Make sure to back-port this to the v12 branch, once you're done.

[laurenceisla]

@wolfgangwalther Just to confirm, cherry-picking and merging to v12 should be enough, right?

[steve-chavez]

Github CI is failing https://www.githubstatus.com/

Update - Customers may see issues running Actions
Jun 11, 2024 - 20:34 UTC

[wolfgangwalther]

@wolfgangwalther Just to confirm, cherry-picking and merging to v12 should be enough, right?

Yes, correct.

[steve-chavez]

I think we should put the actual PostgREST error here. IIRC it says the same but with additional logs.

Something like this should work:

$ postgrest-with-* --replica postgrest-run

Maybe you'll have to edit the withTmp command on the nix file

[laurenceisla]

The error in psql is exactly the same:

postgres=# notify pgrst;
ERROR:  cannot execute NOTIFY during recovery

Now, in the PostgREST 12.2.0 logs, when connecting to a read replica only, it shows:

12/Jun/2024:15:19:57 -0500: Failed listening for notifications on the "pgrst" channel. Just "connection to server on socket \"/run/user/1000/postgrest/postgrest-with-postgresql-16-Y3M/socket_replica_6039/.s.PGSQL.5432\" failed: session is read-only\n"
12/Jun/2024:15:19:57 -0500: Failed listening for notifications on the "pgrst" channel. ExitFailure 1
12/Jun/2024:15:19:57 -0500: Attempting to connect to the database...
12/Jun/2024:15:19:57 -0500: Retrying listening for notifications in 8 seconds...

Are you referring to the latter?

[steve-chavez]

Yeah, maybe just put:

12/Jun/2024:15:19:57 -0500: Failed listening for notifications on the "pgrst" channel... connection to server .. failed: session is read-only

That error message needs fixing btw. Can be another issue.

[steve-chavez]

Ah, damn. I just realized this error doesn't make sense here, it's caused because of our target_session_attrs=read-write.

The previous one with plain SQL was much better. Maybe add something like:

-- check if the instance is a replica
postgres=# select pg_is_in_recovery();
 pg_is_in_recovery 
-------------------
 t
 (1 row)

postgres=# LISTEN pgrst;
<ERROR message here>