Skip to content

Fix lock management problems.#76

Open
manaldush wants to merge 1 commit intopostgrespro:masterfrom
manaldush:lwlock_instead_locktag
Open

Fix lock management problems.#76
manaldush wants to merge 1 commit intopostgrespro:masterfrom
manaldush:lwlock_instead_locktag

Conversation

@manaldush
Copy link

  1. pg_progress_bar should be locked with PG_QS_RCV_KEY, because it is using the same shmem as pg_query_state.
  2. change reqid logic, now it controls backend interruptions.
  3. now all inter-process communication in based on shmem queue reads/sends with appropriate timeouts.
  4. LWLocks used instead locks, it seems quite enough.
  5. Change deadlock test logic, error response are normal in such cases.

1. pg_progress_bar should be locked with PG_QS_RCV_KEY, because
   it is using the same shmem as pg_query_state.
2. change reqid logic, now it controls backend interruptions.
3. now all inter-process communication in based on shmem queue
   reads/sends with appropriate timeouts.
4. LWLocks used instead locks.
5. Change deadlock test logic, error response are normal in such
   cases.
@funny-falcon
Copy link
Contributor

Commit message mentions several not interdependent changes. Commit diff shows it as well.

My opinion, it should be several separate commits. They could be in one Pull Request, if they are somewhat related. But if they are completely independent, then better open pull request for each of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments