Pg_terminate_backend ( pid integer, timeout bigint DEFAULT 0 ) → boolean This works only when the built-in log collector is running, since otherwise there is no log-file manager subprocess. Signals the log-file manager to switch to a new output file immediately. (This is initiated by sending a SIGHUP signal to the postmaster process, which in turn sends SIGHUP to each of its children.) You can use the pg_file_settings and pg_hba_file_rules views to check the configuration files for possible errors, before reloading. Only superusers can request to log the memory contexts.Ĭauses all processes of the PostgreSQL server to reload their configuration files. They will appear in the server log based on the log configuration set (See Section 20.8 for more information), but will not be sent to the client regardless of client_min_messages. These memory contexts will be logged at LOG message level. Requests to log the memory contexts of the backend with the specified process ID. Pg_log_backend_memory_contexts ( pid integer ) → boolean This is also allowed if the calling role is a member of the role whose backend is being canceled or the calling role has been granted pg_signal_backend, however only superusers can cancel superuser backends. Pg_cancel_backend ( pid integer ) → booleanĬancels the current query of the session whose backend process has the specified process ID.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |