mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-12 18:34:36 +08:00
postgres_fdw: Move comments about elog level in (sub)abort cleanup.
The comments were misplaced when adding postgres_fdw. Fix that by moving the comments to more appropriate functions. Author: Etsuro Fujita Backpatch-through: 9.6 Discussion: https://postgr.es/m/CAPmGK164sAXQtC46mDFyu6d-T25Mzvh5qaRNkit06VMmecYnOA%40mail.gmail.com
This commit is contained in:
parent
5b0e7fe1d6
commit
8c7be86883
@ -1137,6 +1137,11 @@ pgfdw_reject_incomplete_xact_state_change(ConnCacheEntry *entry)
|
||||
* and ignore the result. Returns true if we successfully cancel the query
|
||||
* and discard any pending result, and false if not.
|
||||
*
|
||||
* It's not a huge problem if we throw an ERROR here, but if we get into error
|
||||
* recursion trouble, we'll end up slamming the connection shut, which will
|
||||
* necessitate failing the entire toplevel transaction even if subtransactions
|
||||
* were used. Try to use WARNING where we can.
|
||||
*
|
||||
* XXX: if the query was one sent by fetch_more_data_begin(), we could get the
|
||||
* query text from the pendingAreq saved in the per-connection state, then
|
||||
* report the query using it.
|
||||
@ -1187,6 +1192,11 @@ pgfdw_cancel_query(PGconn *conn)
|
||||
* If the query is executed successfully but returns an error, the return
|
||||
* value is true if and only if ignore_errors is set. If the query can't be
|
||||
* sent or times out, the return value is false.
|
||||
*
|
||||
* It's not a huge problem if we throw an ERROR here, but if we get into error
|
||||
* recursion trouble, we'll end up slamming the connection shut, which will
|
||||
* necessitate failing the entire toplevel transaction even if subtransactions
|
||||
* were used. Try to use WARNING where we can.
|
||||
*/
|
||||
static bool
|
||||
pgfdw_exec_cleanup_query(PGconn *conn, const char *query, bool ignore_errors)
|
||||
@ -1233,11 +1243,6 @@ pgfdw_exec_cleanup_query(PGconn *conn, const char *query, bool ignore_errors)
|
||||
* be a query that was initiated as part of transaction abort to get the remote
|
||||
* side back to the appropriate state.
|
||||
*
|
||||
* It's not a huge problem if we throw an ERROR here, but if we get into error
|
||||
* recursion trouble, we'll end up slamming the connection shut, which will
|
||||
* necessitate failing the entire toplevel transaction even if subtransactions
|
||||
* were used. Try to use WARNING where we can.
|
||||
*
|
||||
* endtime is the time at which we should give up and assume the remote
|
||||
* side is dead. Returns true if the timeout expired, otherwise false.
|
||||
* Sets *result except in case of a timeout.
|
||||
|
Loading…
Reference in New Issue
Block a user