备案控制台
探索云世界
开发者社区 安全 文章 正文

PostgreSQL performance test use ssh tunnel

2016-03-31 1908
版权
版权声明：
本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《 阿里云开发者社区用户服务协议》和 《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写 侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
本文涉及的产品
云原生数据库 PolarDB MySQL 版，Serverless 5000PCU 100GB
推荐场景：
PolarDB for MySQL 多主集群体验
简介：
前面一篇BLOG介绍了PostgreSQL ssl数据加密的性能, 相比未加密性能下降得比较厉害.
本文将测试一下ssh tunnel加密的性能情况.
测试机与前面测试一致.

首先在测试机生成key. 
pg92@db-172-16-3-39-> ssh-keygen -t rsa

一路回车
生成私钥和公钥. 
pg92@db-172-16-3-39-> cd .ssh
pg92@db-172-16-3-39-> ll
total 8.0K
-rw------- 1 postgres postgres 887 May 23 07:32 id_rsa
-rw-r--r-- 1 postgres postgres 246 May 23 07:32 id_rsa.pub

查看公钥内容, 将要拷贝到数据库服务器上.
 
pg92@db-172-16-3-39-> cat id_rsa.pub 
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAzRL55hHqAqW8HVQ54fpmZ76QEU6NP/dSdu56bNf61+bVDHl/VHEAlQOAdYI3eCsxCv3BmWDiCFR++LjmnRDU7DvTbWZlKk6xmxlWr9uWgHyXbNLrLSqXm8SapS86ATxTxOvT2w5kEgszFtsgoomrCJhQaVLQFU8geL6IXFNr5/g4nK1R2GbQH4eoBFE1a0eh61OhY6+Jq0eaKhZqaLI+Ed8Q5Ce5JjyG8DGhzY2S63OFpncCN2qTjjh8Vhl4SlwF/XZmCZILEfKHUVCi/jKnC068yfcvNl5QmSw2FlELpWFkoxNiCGarSpgXTC3CigBuKmcjR+z7gbHrhbSgnpM4fQ== pg92@db-172-16-3-39.sky-mobi.com

在数据库服务器上写入公钥.
 
[root@db-172-16-3-33 ~]# su - pg93
pg93@db-172-16-3-33-> cd .ssh
-bash: cd: .ssh: No such file or directory
pg93@db-172-16-3-33-> mkdir .ssh
pg93@db-172-16-3-33-> cd .ssh
pg93@db-172-16-3-33-> vi authorized_keys

将172.16.3.39的id_rsa.pub复制过来.
配置各目录权限 : 
pg93@db-172-16-3-33-> cd ~
pg93@db-172-16-3-33-> chmod 700 ~
pg93@db-172-16-3-33-> chmod 700 .ssh
pg93@db-172-16-3-33-> chmod 400 .ssh/authorized_keys

验证公钥是否生效, 不需要输入密码则正常.
 
pg92@db-172-16-3-39-> ssh pg93@172.16.3.33 date
Thu May 23 07:37:14 CST 2013

在测试机上创建连接到数据库服务器的ssh隧道,
 
pg92@db-172-16-3-39-> ssh -o CompressionLevel=9 -p 22 -CqTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
pg92@db-172-16-3-39-> netstat -anp|grep 17100
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:17100               0.0.0.0:*                   LISTEN      12954/ssh

# 测试通过隧道连接数据库是否正常.
 
pg92@db-172-16-3-39-> psql -h 127.0.0.1 -p 17100 -U postgres -d digoal
psql (9.2beta1, server 9.3devel)
WARNING: psql version 9.2, server version 9.3.
         Some psql features might not work.
SSL connection (cipher: RC4-SHA, bits: 128)
Type "help" for help.
digoal=#

此时数据库服务端开了hostssl认证, 因为用了ssh加密, 所以ssl加密可以关掉.
修改pg_hba.conf, 强制nossl认证. 
pg93@db-172-16-3-33-> cd $PGDATA
pg93@db-172-16-3-33-> vi pg_hba.conf 
hostnossl    all             all             127.0.0.1/32            trust

pg_ctl reload

再次连接, 无加密.
 
pg92@db-172-16-3-39-> psql -h 127.0.0.1 -p 17100 -U postgres -d digoal
psql (9.2beta1, server 9.3devel)
WARNING: psql version 9.2, server version 9.3.
         Some psql features might not work.
Type "help" for help.
digoal=#


测试性能,
与上一篇blog测试openssl配置的环境一致, 好有个对比.
测试结果 : 
pg92@db-172-16-3-39-> pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 16 -j 4 digoal
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 16
number of threads: 4
duration: 60 s
number of transactions actually processed: 1008287
tps = 16804.427360 (including connections establishing)
tps = 16818.105936 (excluding connections establishing)


关闭隧道压缩, 再次测试 : 
 
pg92@db-172-16-3-39-> ps -ewf|grep ssh
root       949     1  0 Mar21 ?        00:00:00 /usr/sbin/sshd
root      7681   949  0 May22 ?        00:00:00 sshd: root@pts/0 
root      9022   949  0 May22 ?        00:00:00 sshd: root@pts/2 
pg92     12954     1 18 07:57 ?        00:00:47 ssh -o CompressionLevel=9 -p 22 -CqTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
pg92     12984 12904  0 08:01 pts/0    00:00:00 grep ssh
pg92@db-172-16-3-39-> kill 12954
pg92@db-172-16-3-39-> ssh -p 22 -o "Compression no" -qTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33

测试结果 : 
 
pg92@db-172-16-3-39-> pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 16 -j 4 digoal
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 16
number of threads: 4
duration: 60 s
number of transactions actually processed: 434617
tps = 7241.081323 (including connections establishing)
tps = 7247.051105 (excluding connections establishing)


开启压缩, 并更改加密暗语为blowfish:
 
pg92@db-172-16-3-39-> ps -ewf|grep ssh
root       949     1  0 Mar21 ?        00:00:00 /usr/sbin/sshd
root      7681   949  0 May22 ?        00:00:00 sshd: root@pts/0 
root      9022   949  0 May22 ?        00:00:00 sshd: root@pts/2 
pg92     13051     1 11 08:04 ?        00:00:18 ssh -p 22 -o Compression=no -qTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
pg92     13067 12904  0 08:06 pts/0    00:00:00 grep ssh
pg92@db-172-16-3-39-> kill 13051
pg92@db-172-16-3-39-> ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33

测试结果 : 
 
pg92@db-172-16-3-39-> pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 16 -j 4 digoal
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 16
number of threads: 4
duration: 60 s
number of transactions actually processed: 1039471
tps = 17323.172100 (including connections establishing)
tps = 17338.330403 (excluding connections establishing)


[小结]
1. 使用ssh 隧道比直接在数据库上配置ssl加密要慢, 因为只使用了1个隧道.
如果建立多个隧道会不会更好一点呢?
建立8个隧道. 
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17101:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17102:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17103:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17104:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17105:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17106:127.0.0.1:1999 pg93@172.16.3.33
ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17107:127.0.0.1:1999 pg93@172.16.3.33


pg92@db-172-16-3-39-> ps -ewf|grep ssh|grep -v grep
root       949     1  0 Mar21 ?        00:00:00 /usr/sbin/sshd
root      7681   949  0 May22 ?        00:00:00 sshd: root@pts/0 
root      9022   949  0 May22 ?        00:00:00 sshd: root@pts/2 
pg92     13204     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
pg92     13210     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17101:127.0.0.1:1999 pg93@172.16.3.33
pg92     13216     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17102:127.0.0.1:1999 pg93@172.16.3.33
pg92     13222     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17103:127.0.0.1:1999 pg93@172.16.3.33
pg92     13228     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17104:127.0.0.1:1999 pg93@172.16.3.33
pg92     13234     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17105:127.0.0.1:1999 pg93@172.16.3.33
pg92     13240     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17106:127.0.0.1:1999 pg93@172.16.3.33
pg92     13246     1  0 08:34 ?        00:00:00 ssh -o CompressionLevel=9 -c blowfish -p 22 -CqTfnN -L *:17107:127.0.0.1:1999 pg93@172.16.3.33

测试 : 
 
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17101 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17102 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17103 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17104 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17105 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17106 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17107 -U postgres -T 60 -c 2 -j 1 digoal &

pg92@db-172-16-3-39-> jobs
[1]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 2 -j 1 digoal &
[2]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17101 -U postgres -T 60 -c 2 -j 1 digoal &
[3]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17102 -U postgres -T 60 -c 2 -j 1 digoal &
[4]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17103 -U postgres -T 60 -c 2 -j 1 digoal &
[5]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17104 -U postgres -T 60 -c 2 -j 1 digoal &
[6]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17105 -U postgres -T 60 -c 2 -j 1 digoal &
[7]-  Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17106 -U postgres -T 60 -c 2 -j 1 digoal &
[8]+  Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17107 -U postgres -T 60 -c 2 -j 1 digoal &

测试结果 : 
 
pg92@db-172-16-3-39-> transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 221246
tps = 3687.366100 (including connections establishing)
tps = 3693.281275 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 224540
tps = 3742.294039 (including connections establishing)
tps = 3745.909116 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 222014
tps = 3700.200155 (including connections establishing)
tps = 3703.833274 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 225675
tps = 3761.186749 (including connections establishing)
tps = 3765.324960 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 226583
tps = 3776.300569 (including connections establishing)
tps = 3782.679035 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 230229
tps = 3837.095577 (including connections establishing)
tps = 3841.695622 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 226564
tps = 3775.985231 (including connections establishing)
tps = 3782.328437 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 218551
tps = 3642.426638 (including connections establishing)
tps = 3648.666129 (excluding connections establishing)

合计比单个端口代理要高, 但是比直接使用ssl加密要低.

关闭压缩测试, 比以上测试tps略高 : 
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17101:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17102:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17103:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17104:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17105:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17106:127.0.0.1:1999 pg93@172.16.3.33
ssh -o "Compression no" -c blowfish -p 22 -qTfnN -L *:17107:127.0.0.1:1999 pg93@172.16.3.33

pg92@db-172-16-3-39->  ps -ewf|grep ssh|grep -v grep
root       949     1  0 Mar21 ?        00:00:00 /usr/sbin/sshd
root      7681   949  0 May22 ?        00:00:00 sshd: root@pts/0 
root      9022   949  0 May22 ?        00:00:00 sshd: root@pts/2 
pg92     13294     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17100:127.0.0.1:1999 pg93@172.16.3.33
pg92     13300     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17101:127.0.0.1:1999 pg93@172.16.3.33
pg92     13306     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17102:127.0.0.1:1999 pg93@172.16.3.33
pg92     13312     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17103:127.0.0.1:1999 pg93@172.16.3.33
pg92     13318     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17104:127.0.0.1:1999 pg93@172.16.3.33
pg92     13324     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17105:127.0.0.1:1999 pg93@172.16.3.33
pg92     13330     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17106:127.0.0.1:1999 pg93@172.16.3.33
pg92     13336     1  0 08:38 ?        00:00:00 ssh -o Compression no -c blowfish -p 22 -qTfnN -L *:17107:127.0.0.1:1999 pg93@172.16.3.33

测试 : 
 
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17101 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17102 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17103 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17104 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17105 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17106 -U postgres -T 60 -c 2 -j 1 digoal &
pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17107 -U postgres -T 60 -c 2 -j 1 digoal &

pg92@db-172-16-3-39-> jobs
[1]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17100 -U postgres -T 60 -c 2 -j 1 digoal &
[2]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17101 -U postgres -T 60 -c 2 -j 1 digoal &
[3]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17102 -U postgres -T 60 -c 2 -j 1 digoal &
[4]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17103 -U postgres -T 60 -c 2 -j 1 digoal &
[5]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17104 -U postgres -T 60 -c 2 -j 1 digoal &
[6]   Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17105 -U postgres -T 60 -c 2 -j 1 digoal &
[7]-  Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17106 -U postgres -T 60 -c 2 -j 1 digoal &
[8]+  Running                 pgbench -M prepared -n -f ./sel.sql -h 127.0.0.1 -p 17107 -U postgres -T 60 -c 2 -j 1 digoal &

测试结果 : 
pg92@db-172-16-3-39-> transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 231898
tps = 3864.904506 (including connections establishing)
tps = 3871.202723 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 234955
tps = 3915.837110 (including connections establishing)
tps = 3924.836512 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 241359
tps = 4022.581549 (including connections establishing)
tps = 4032.042374 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 237272
tps = 3954.495436 (including connections establishing)
tps = 3960.789268 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 235486
tps = 3924.681501 (including connections establishing)
tps = 3933.783948 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 245445
tps = 4090.663073 (including connections establishing)
tps = 4097.263762 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 233128
tps = 3885.425157 (including connections establishing)
tps = 3889.080854 (excluding connections establishing)
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 2
number of threads: 1
duration: 60 s
number of transactions actually processed: 238585
tps = 3976.336212 (including connections establishing)
tps = 3982.943184 (excluding connections establishing)

合计比单个端口代理要高, 但是比直接使用ssl加密要低.

[参考]
4. man ssh 
     -c cipher_spec
             Selects the cipher specification for encrypting the session.

             Protocol version 1 allows specification of a single cipher.  The supported values are “3des”, “blowfish”,
             and “des”.  3des (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.  It is
             believed to be secure.  blowfish is a fast block cipher; it appears very secure and is much faster than
             3des.  des is only supported in the ssh client for interoperability with legacy protocol 1 implementa-
             tions that do not support the 3des cipher.  Its use is strongly discouraged due to cryptographic weak-
             nesses.  The default is “3des”.

             For protocol version 2, cipher_spec is a comma-separated list of ciphers listed in order of preference.
             The supported ciphers are: 3des-cbc, aes128-cbc, aes192-cbc, aes256-cbc, aes128-ctr, aes192-ctr,
             aes256-ctr, arcfour128, arcfour256, arcfour, blowfish-cbc, and cast128-cbc.  The default is:

                   aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
                   arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
                   aes192-ctr,aes256-ctr

文章标签：
云原生数据库 PolarDB
密钥管理服务
网络安全
关系型数据库
数据安全/隐私保护
数据库
关键词：
云原生数据库 PolarDB use
云原生数据库 PolarDB ssh
相关实践学习
使用PolarDB和ECS搭建门户网站
本场景主要介绍基于PolarDB和ECS实现搭建门户网站。
阿里云数据库产品家族及特性
阿里云智能数据库产品团队一直致力于不断健全产品体系，提升产品性能，打磨产品功能，从而帮助客户实现更加极致的弹性能力、具备更强的扩展能力、并利用云设施进一步降低企业成本。以云原生+分布式为核心技术抓手，打造以自研的在线事务型(OLTP)数据库Polar DB和在线分析型(OLAP)数据库Analytic DB为代表的新一代企业级云原生数据库产品体系， 结合NoSQL数据库、数据库生态工具、云原生智能化数据库管控平台，为阿里巴巴经济体以及各个行业的企业客户和开发者提供从公共云到混合云再到私有云的完整解决方案，提供基于云基础设施进行数据从处理、到存储、再到计算与分析的一体化解决方案。本节课带你了解阿里云数据库产品家族及特性。
德哥,digoal
目录
相关文章
德哥,digoal
|
关系型数据库 网络安全 数据库
PostgreSQL hostssl auth use openssl - Encrypting Data Across A Network
德哥,digoal
1618 0
德哥,digoal
|
关系型数据库 PostgreSQL
PostgreSQL sharding : citus 系列7 - topn 加速(count(*) group by order by count(*) desc limit x) (use 估值插件 topn)
标签 PostgreSQL , topn , topn.number_of_counters , count(*) group by order by count(*) desc limit x 背景 count(*) group by order by count(*) desc limit x 用来统计 topn。
德哥,digoal
1367 0
德哥,digoal
|
关系型数据库 PostgreSQL
PostgreSQL sharding : citus 系列6 - count(distinct xx) 加速 (use 估值插件 hll|hyperloglog)
标签 PostgreSQL , hll , hyperloglog , distinct , 加速 , citus.count_distinct_error_rate 背景 在分布式数据库中，计算count(distinct xxx)，需要对distinct 的字段， 1、去重， 2、重分布去重后的数据，（这一步，如果distinct值特别多，那么就会比较耗时） 3、然后再去重， 4、最后count (xxx)， 5、求所有节点的count SUM。
德哥,digoal
1783 0
德哥,digoal
|
弹性计算 关系型数据库 测试技术
PostgreSQL 11 tpcc 测试(103万tpmC on ECS) - use sysbench-tpcc by Percona-Lab
标签 PostgreSQL , tpcc 背景 环境 阿里云虚拟机 [root@pg11-test ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: ...
德哥,digoal
4107 0
李博 bluemind
|
安全 网络安全 数据库
PostgreSQL 10.1 手册_部分 III. 服务器管理_第 18 章 服务器设置和操作_18.10. 使用SSH隧道的安全 TCP/IP 连接
18.10. 使用SSH隧道的安全 TCP/IP 连接 可以使用SSH来加密客户端和PostgreSQL服务器之间的网络连接。如果处理得当，这将提供一个足够安全的网络连接，即使是对那些无 SSL 能力的客户端。
李博 bluemind
1161 0
德哥,digoal
|
关系型数据库 PostgreSQL
PostgreSQL central stream replication unlinked use (scp, cp, pg_basebackup ...)
德哥,digoal
1573 0
德哥,digoal
|
Oracle 关系型数据库 数据库连接
Oracle Connect To PostgreSQL use HS DBLINK
德哥,digoal
4309 0
德哥,digoal
|
关系型数据库
PostgreSQL per database or per user audit use pg_log_userqueries
德哥,digoal
1796 0
德哥,digoal
|
SQL 安全 关系型数据库
PostgreSQL security - don't use password method in pg_hba.conf
德哥,digoal
1839 0
德哥,digoal
|
算法 关系型数据库 数据库
PostgreSQL column cryptographic use pgcrypto extension and optional openssl lib
德哥,digoal
3563 0

热门文章

最新文章

  • 1
    PolarDB +AnalyticDB Zero-ETL ：免费同步数据到ADB，享受数据流通新体验
  • 2
    PolarDB常见问题之PolarDB冷存数据到OSS之后恢复失败如何解决
  • 3
    PolarDB常见问题之PolarDB影响下游的binlogl同步如何解决
  • 4
    成都晨云信息技术完成阿里云PolarDB数据库产品生态集成认证
  • 5
    开发者视角看云原生数据库一体化技术趋势
  • 6
    课程导航 | 学姐领航，共学PolarDB-X：从入门到精通实操课
  • 7
    如何看待云原生数据库一体化的技术趋势？
  • 8
    利用Helm在K8S上部署 PolarDB-X 集群（详细步骤--亲测！！！）
  • 9
    数据之势丨AI时代，云原生数据库的最新发展趋势与进展
  • 10
    PostgreSQL从小白到高手教程 - 第48讲：PG高可用实现keepalived
  • 1
    TiDB与MySQL、PostgreSQL等数据库的比较分析
    81
  • 2
    PostgreSQL从小白到高手教程 - 第47讲：JMETER工具使用
    106
  • 3
    PostgreSQL从小白到高手教程 - 第46讲：poc-tpch测试
    83
  • 4
    一篇文章带你搞懂非关系型数据库MongoDB
    55
  • 5
    PolarDB中的pdb冷归档存储和X-Engine的价格对比
    14
  • 6
    PolarDB的Serverless能力与同类型产品的对比
    18
  • 7
    DataWorks常见问题之将预警信息发送至邮箱
    35
  • 8
    PolarDB for MySQL数据库外网连接解析失败的原因可能有以下几点
    23
  • 9
    PolarDB架构优势
    473
  • 10
    PolarDB架构
    424

    • 相关课程

    更多
  • 7天突破PolarDB for PostgreSQL 2022版
  • 关系型数据库ACP认证课程
  • 关系型数据库线上预习视频
  • PolarDB for PostgreSQL 入门
  • PostgreSQL云上开发实践
  • PostgreSQL实战进阶

    • 相关电子书

    更多
  • 2023云栖大会：和客户一起玩转PolarDB新特性
  • 2023云栖大会：PolarDB for AI
  • 2023云栖大会：AnalyticDB PostgreSQL

    • 相关实验场景

    更多
  • PolarDB NL2SQL：自然语言驱动的数据智能
  • 阿里云百炼xAnalyticDB PostgreSQL构建AIGC应用
  • 云原生数据库PolarDB快速入门
  • PolarDB for AI：在数据库中通过SQL实现AI能力
  • 使用CloudLens采集PolarDB日志并进行审计分析
  • PolarDB for PostgreSQL 闪回特性体验

    • 推荐镜像

    更多
  • postgresql
  • clickhouse
  • mysql
    • 下一篇
    阿里云oss简介和使用流程