In operator.go there are a number of functions including ScalarOperatorTransmitsNulls, BoolOperatorRequiresNotNullArgs, AggregateIgnoresNulls, AggregateIsNullOnEmpty, AggregateIsNeverNullOnNonNullInput, AggregateIsNeverNull, AggregatesCanMerge, and AggregateIgnoresDuplicates that serve as facts about di

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

Same as #7883

• org.apache.shardingsphere.governance.repository.etcd.EtcdRepository
• org.apache.shardingsphere.governance.repository.etcd.EtcdRepositoryTest

The old restore supports adding prefix and suffix to the backup data. This allows us to restore a key space (say [a, b)) to a new key space (say [awesome_a, awesome_b).

This feature is useful in:

• Performance testing: We do not want to throw away existing loaded data in the cluster because loading a huge DB takes time;
• Cross-verification: Users may want to verify the restored data in the

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-

There doesn't seem to be a way to set postgres process options without editing the source code and compiling. Add a gflag to take those options, and make sure they override the defaults (whether that be making the options after the defaults or before, I don't know at the moment).

One use of this is using the -d N option to set different log levels (e.g. DEBUG3) for postgres. See `src/po

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

See io.prestosql.operator.scalar.timestamptz.TestExtract for a starting point.

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