Monitors wire protocol messages during a Live Share session and automatically updates the schema UI to reflect the current state.
Background
In order to update the schema UI, we need to query the PGlite instance (via pg-meta) to get the latest tables/columns. Since this requires executing SQL against the same PGlite instance that Live Share is communicating with, we need to be careful not to run this when the user is in the middle of set of protocol messages (eg. extended queries).
When is it safe?
We update the UI after detecting a ReadyForQuery response from PGlite, which indicates that the current set of protocol messages have completed and a fresh query is safe to execute. We also ensure that the connection is not in the middle of a transaction by checking a transaction status flag sent with the ReadyForQuery message.
Monitors wire protocol messages during a Live Share session and automatically updates the schema UI to reflect the current state.
Background
In order to update the schema UI, we need to query the PGlite instance (via pg-meta) to get the latest tables/columns. Since this requires executing SQL against the same PGlite instance that Live Share is communicating with, we need to be careful not to run this when the user is in the middle of set of protocol messages (eg. extended queries).
When is it safe?
We update the UI after detecting a
ReadyForQuery
response from PGlite, which indicates that the current set of protocol messages have completed and a fresh query is safe to execute. We also ensure that the connection is not in the middle of a transaction by checking a transaction status flag sent with theReadyForQuery
message.