The PGJDBC docs describe how one can include a URL parameter of options in order to set session variables: https://jdbc.postgresql.org/documentation/head/connect.html#connection-parameters

This is important because PGJDBC does not allow one to set session variables directly in the URL. That is, you need to specify like this:

postgresql://user@host:port/database?options=-c%20serial_nor

Now insert and query share the resource ( Max Process Count control) 。 When the query with high TPS，the insert will get error (“error: too many process”). I think separator the resource for Insert and Query will makes sense. Ensure enough resource for insert。It looks like Use Yarn， Insert and Query use the different resource quota。
Or the simple way , Can we set Ratio for Insert and

The network option setting code uses the default option code, which interprets the bytes passed to the option as a binary encoded 8 byte integer. The only way to set an integer value is to set the environment variable to the 8 byte binary encoding.

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

See https://docs.yugabyte.com/latest/admin/yb-admin/#modify-placement-info for the current usage of modify-placement-info. Currently this precludes users from specifying how many replicas belong in each availability zone specified. To fix, this make the placement_info field a comma separated list of cloud1.datacenter1.rack1:num_replicas.

Currently, we test Parquet with default config, but not with the optimized writer.

See #6382.

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)

Currently a cache node object consists of a Key, a Value and a TTL. We should also add a field specifying the type of the Value