PolarDB产品使用合集之有的sql里面有自定义存储函数 如果想走列存有什么优化建议吗

简介: PolarDB是阿里云推出的一种云原生数据库服务,专为云设计,提供兼容MySQL、PostgreSQL的高性能、低成本、弹性可扩展的数据库解决方案,可以有效地管理和优化PolarDB实例,确保数据库服务的稳定、高效运行。以下是使用PolarDB产品的一些建议和最佳实践合集。

问题一:PolarDB开启binlog实现主从复制会对性能有多大影响呢?


PolarDB开启binlog实现主从复制会对性能有多大影响呢?


参考回答:

很大,写性能差一倍以上。


关于本问题的更多回答可点击原文查看:https://developer.aliyun.com/ask/584072


问题二:polarDB和mariaDB实现binlog主从复制怎么弄?


polarDB和mariaDB实现binlog主从复制怎么弄?polarDB为主,mariaDB为从实现主从同步


参考回答:

参考mysql与mariadb同步,一模一样。


关于本问题的更多回答可点击原文查看:https://developer.aliyun.com/ask/584071


问题三:PolarDB这个问题怎么解决? max没有排序语义 sql语义变了


PolarDB这个问题怎么解决? max没有排序语义 sql语义变了,改成这种窗口函数实现 可以走列存 也非常慢 直接把ap节点cpu拉满了,SELECT ep.product_id, p.products_name AS products_name_m, p.products_url_name, ep.enterprise_id, ent.enterprise_name_en AS enterprise_name

, ent.url_name AS enterprise_url_name, ep.specification, DATE_FORMAT(ep.price_date, '%Y-%m-%d') AS price_date

, ep.price_unit, ep.price AS current_price

, (

SELECT tmp.price

FROM (

SELECT ep2.price, ROW_NUMBER() OVER (PARTITION BY ep2.product_id ORDER BY ep2.price_date DESC) AS rank_no

FROM echemi_db_v0_3.t_zy_enterprise_price ep2

LEFT JOIN t_zy_enterprise_price ep

ON ep2.product_id = ep.product_id

AND ep2.enterprise_id = ep.enterprise_id

WHERE IFNULL(ep2.delflag, '') <> '1'

AND ep2.price_date < ep.price_date

AND IFNULL(ep2.price_date, '') != ''

AND IFNULL(ep2.price, '') != ''

AND IFNULL(ep2.delflag, '') != '1'

) tmp

WHERE tmp.rank_no = 1

) AS previous_price, 0 AS subscribe_flag

FROM t_zy_enterprise_price ep

INNER JOIN t_e_products p

ON p.products_id = ep.product_id

AND p.information_flag = '1'

AND IFNULL(p.delflag, '0') != '1'

INNER JOIN t_zy_enterprise ent

ON ent.id = ep.enterprise_id

AND IFNULL(ent.delflag, '0') != '1'

INNER JOIN (

SELECT ep3.product_id, ep3.enterprise_id, MAX(ep3.price_date) AS max_price_date

FROM t_zy_enterprise_price ep3

GROUP BY ep3.product_id, ep3.enterprise_id

) pimax

ON pimax.product_id = ep.product_id

AND pimax.enterprise_id = ep.enterprise_id

AND pimax.max_price_date = ep.price_date

WHERE ep.delflag = '0'

ORDER BY subscribe_flag DESC, ep.price_date DESC, ep.update_date DESC, ep.id

LIMIT 5


参考回答:

那得用window改,SELECT

tmp1.*,

(

SELECT

tmp.price

FROM

(

SELECT

ep2.price,

ROW_NUMBER() OVER (

PARTITION BY ep2.product_id

ORDER BY

ep2.price_date DESC

) AS rank_no

FROM

echemi_db_v0_3.t_zy_enterprise_price ep2

LEFT JOIN t_zy_enterprise_price ep ON ep2.product_id = ep.product_id

AND ep2.enterprise_id = ep.enterprise_id

WHERE

IFNULL(ep2.delflag, '') <> '1'

AND ep2.price_date < ep.price_date

AND IFNULL(ep2.price_date, '') != ''

AND IFNULL(ep2.price, '') != ''

AND IFNULL(ep2.delflag, '') != '1'

) tmp

WHERE

tmp.rank_no = 1

) AS previous_price,

0 AS subscribe_flag

FROM

(

SELECT

ep.product_id,

p.products_name AS products_name_m,

p.products_url_name,

ep.enterprise_id,

ent.enterprise_name_en AS enterprise_name,

ent.url_name AS enterprise_url_name,

ep.specification,

DATE_FORMAT(ep.price_date, '%Y-%m-%d') AS price_date,

ep.price_unit,

ep.price AS current_price,

ep.price_date as pd,

ep.update_date as ud,

ep.id as id

FROM

t_zy_enterprise_price ep

INNER JOIN t_e_products p ON p.products_id = ep.product_id

AND p.information_flag = '1'

AND IFNULL(p.delflag, '0') != '1'

INNER JOIN t_zy_enterprise ent ON ent.id = ep.enterprise_id

AND IFNULL(ent.delflag, '0') != '1'

INNER JOIN (

SELECT

ep3.product_id,

ep3.enterprise_id,

MAX(ep3.price_date) AS max_price_date

FROM

t_zy_enterprise_price ep3

GROUP BY

ep3.product_id,

ep3.enterprise_id

) pimax ON pimax.product_id = ep.product_id

AND pimax.enterprise_id = ep.enterprise_id

AND pimax.max_price_date = ep.price_date

WHERE

ep.delflag = '0'

ORDER BY

subscribe_flag DESC,

ep.price_date DESC,

ep.update_date DESC,

ep.id

LIMIT

5

) tmp1

ORDER BY

subscribe_flag DESC,

tmp1.pd DESC,

tmp1.ud DESC,

tmp1.id

LIMIT

5

试试这个,先做LIMIT 5减少下window的计算量,也可以试试把

SELECT ep2.price, ep2.price_date FROM t_zy_enterprise_price ep2 ORDER BY ep2.price_date DESC, ep2.price desc limit 1;

改为

select max(ep2.price) FROM t_zy_enterprise_price ep2 where ep2.price_date = (SELECT max(price_date) from t_zy_enterprise_price);


关于本问题的更多回答可点击原文查看:https://developer.aliyun.com/ask/584070


问题四:在PolarDB有的sql里面有自定义存储函数 这种想走列存有什么优化建议吗?


在PolarDB有的sql里面有自定义存储函数 还有的子查询里面有limit语句的 这种想走列存有什么优化建议吗?自定义函数例如这种SELECT

a.*,

func_create_url_name(a.title) AS url_name

FROM

(

SELECT

con.contentid,

con.catid,

cat.name AS catname,

cat.abbr AS catabbr,

con.modelid,

con.title,

con.subtitle,

con.url AS info_url,

con.tags AS tags,

con.tags AS original_tags,

CASE

WHEN LOWER(LEFT(con.thumb, 4)) = 'http' THEN con.thumb

ELSE CONCAT('https://xxx/', con.thumb)

END AS thumb,

con.published,

con.pv

FROM

cmstop_content con

INNER JOIN cmstop_category cat ON cat.catid = con.catid

AND cat.first_parentid = '201'

AND FIND_IN_SET('204', cat.parentids)

INNER JOIN (

SELECT

content_tag.contentid

FROM

cmstop_tag tag

INNER JOIN cmstop_content_tag content_tag ON tag.tagid = content_tag.tagid

WHERE

tag.tag = 'zyp-pd2202071028'

) content_tag ON con.contentid = content_tag.contentid

WHERE

con.status = 6

AND con.modelid IN (1, 3, 4, 10)

ORDER BY

con.published DESC,

con.contentid DESC

LIMIT

1

) a

还有这种子查询有limit的。SELECT

ep.product_id,

p.products_name AS products_name_m,

p.products_url_name,

ep.enterprise_id,

ent.enterprise_name_en AS enterprise_name,

ent.url_name AS enterprise_url_name,

ep.specification,

DATE_FORMAT(ep.price_date, '%Y-%m-%d') AS price_date,

ep.price_unit,

ep.price AS current_price,

(

SELECT

ep2.price

FROM

t_zy_enterprise_price ep2

WHERE

ep2.product_id = ep.product_id

AND ep2.enterprise_id = ep.enterprise_id

AND ep2.price_date < ep.price_date

AND IFNULL(ep2.price_date, '') != ''

AND IFNULL(ep2.price, '') != ''

AND IFNULL(ep2.delflag, '') != '1'

ORDER BY

ep2.price_date DESC

LIMIT

1

) AS previous_price,

0 AS subscribe_flag

FROM

t_zy_enterprise_price ep

INNER JOIN t_e_products p ON p.products_id = ep.product_id

AND p.information_flag = '1'

AND IFNULL(p.delflag, '0') != '1'

INNER JOIN t_zy_enterprise ent ON ent.id = ep.enterprise_id

AND IFNULL(ent.delflag, '0') != '1'

INNER JOIN (

SELECT

ep3.product_id,

ep3.enterprise_id,

MAX(ep3.price_date) AS max_price_date

FROM

t_zy_enterprise_price ep3

GROUP BY

ep3.product_id,

ep3.enterprise_id

) pimax ON pimax.product_id = ep.product_id

AND pimax.enterprise_id = ep.enterprise_id

AND pimax.max_price_date = ep.price_date

WHERE

ep.delflag = '0'

ORDER BY

subscribe_flag DESC,

ep.price_date DESC,

ep.update_date DESC,

ep.id

LIMIT

5

CREATE DEFINER=young@% FUNCTION func_create_url_name(

p_str varchar(500) charset utf8mb4 collate utf8mb4_general_ci ) RETURNS varchar(500) CHARSET utf8

SQL SECURITY INVOKER

BEGIN

DECLARE urlName VARCHAR(500);

SET urlName = p_str;

SET urlName = REPLACE(urlName,'β','');

SET urlName = REPLACE(urlName,'α','');

SET urlName = REPLACE(urlName,'ω','');

SET urlName = REPLACE(urlName,'~', '');

SET urlName = REPLACE(urlName,'!', '');

SET urlName = REPLACE(urlName,'!', '');

SET urlName = REPLACE(urlName,'#', '');

SET urlName = REPLACE(urlName,'$', '');

SET urlName = REPLACE(urlName,'¥', '');

SET urlName = REPLACE(urlName,'¥', '');

SET urlName = REPLACE(urlName,'^', '');

SET urlName = REPLACE(urlName,'*', '');

SET urlName = REPLACE(urlName,'%', '');

SET urlName = REPLACE(urlName,';', '');

SET urlName = REPLACE(urlName,';', '');

SET urlName = REPLACE(urlName,'.', '');

SET urlName = REPLACE(urlName,'。', '');

SET urlName = REPLACE(urlName,'·', '');

SET urlName = REPLACE(urlName,'+', '');

SET urlName = REPLACE(urlName,'=', '');

SET urlName = REPLACE(urlName,':', '');

SET urlName = REPLACE(urlName,':', '');

SET urlName = REPLACE(urlName,'>', '');

SET urlName = REPLACE(urlName,'<', '');

SET urlName = REPLACE(urlName,'》', '');

SET urlName = REPLACE(urlName,'《', '');

SET urlName = REPLACE(urlName,'[', '');

SET urlName = REPLACE(urlName,']', '');

SET urlName = REPLACE(urlName,'【', '');

SET urlName = REPLACE(urlName,'】', '');

SET urlName = REPLACE(urlName,'{', '');

SET urlName = REPLACE(urlName,'}', '');

SET urlName = REPLACE(urlName,'(', '');

SET urlName = REPLACE(urlName,')', '');

SET urlName = REPLACE(urlName,'(', '');

SET urlName = REPLACE(urlName,')', '');

SET urlName = REPLACE(urlName,'、', '');

SET urlName = REPLACE(urlName,'|', '');

SET urlName = REPLACE(urlName,'™', '');

SET urlName = REPLACE(urlName,'®', '');

SET urlName = REPLACE(urlName,'©', '');

SET urlName = REPLACE(urlName,'?', '');

SET urlName = REPLACE(urlName,'?', '');

SET urlName = REPLACE(urlName,'\'', ' ');

SET urlName = REPLACE(urlName,'"', ' ');

SET urlName = REPLACE(urlName,'&', ' ');

SET urlName = REPLACE(urlName,'—', ' ');

SET urlName = REPLACE(urlName,'/', ' ');

SET urlName = REPLACE(urlName,'\', ' ');

SET urlName = REPLACE(urlName,',', ' ');

SET urlName = REPLACE(urlName,',', ' ');

SET urlName = REPLACE(urlName,' ', ' ');

SET urlName = REPLACE(urlName,' ', ' ');

SET urlName = REPLACE(urlName,' ', ' ');

SET urlName = REPLACE(urlName,' ', '-');

SET urlName = REPLACE(urlName,'----', '-');

SET urlName = REPLACE(urlName,'---', '-');

SET urlName = REPLACE(urlName,'--', '-');

SET urlName = TRIM(urlName);

SET urlName = TRIM(BOTH '-' FROM urlName);

SET urlName = LOWER(urlName);

return urlName;

END


参考回答:

自定义函数里面有控制语句,还在调研中。SELECT

ep2.price

FROM

t_zy_enterprise_price ep2

ORDER BY

ep2.price_date DESC

LIMIT

1

可以改成

SELECT

MAX(ep2.price)

FROM

t_zy_enterprise_price ep2 最后一个函数可以直接让业务处理a.title。


关于本问题的更多回答可点击原文查看:https://developer.aliyun.com/ask/584069


问题五:PolarDB这种sql为啥也不走列存呢 ?我改了下发现还不走 。


PolarDB这种sql为啥也不走列存呢 ?我改了下发现还不走。SELECT DISTINCT sk.search_type, sk.search_keywords FROM t_e_search_keywords sk WHERE sk.search_type = '1' AND sk.ip = ' 139.5.31.25' AND LENGTH(sk.search_keywords) = CHAR_LENGTH(sk.search_keywords) ORDER BY sk.search_time DESC LIMIT 10;SELECT DISTINCT sk.search_type, sk.search_keywords,sk.search_time FROM t_e_search_keywords sk WHERE sk.search_type = '1' AND sk.ip = ' 139.5.31.25' AND LENGTH(sk.search_keywords) = CHAR_LENGTH(sk.search_keywords) ORDER BY


参考回答:

第一条是不会走的,得升级; 第二条应该是可以的,针对order by limit 这些sql在一些情况下代价估算不太准确, 导致cost比较小就路由到行存了, 刚才配置一些选项, 断开连接试试,不行再show variables like '%imci%opt%'; 试试。


关于本问题的更多回答可点击原文查看:https://developer.aliyun.com/ask/584068


相关文章
|
6月前
|
关系型数据库 MySQL 分布式数据库
安全可靠的PolarDB V2.0 (兼容MySQL)产品能力及应用场景
PolarDB分布式轻量版采用软件输出方式,能够部署在您的自主环境中。PolarDB分布式轻量版保留并承载了云原生数据库PolarDB分布式版技术团队深厚的内核优化成果,在保持高性能的同时,显著降低成本。
655 140
|
4月前
|
SQL 数据可视化 关系型数据库
MCP与PolarDB集成技术分析:降低SQL门槛与简化数据可视化流程的机制解析
阿里云PolarDB与MCP协议融合,打造“自然语言即分析”的新范式。通过云原生数据库与标准化AI接口协同,实现零代码、分钟级从数据到可视化洞察,打破技术壁垒,提升分析效率99%,推动企业数据能力普惠化。
408 3
|
6月前
|
存储 关系型数据库 分布式数据库
喜报|阿里云PolarDB数据库(分布式版)荣获国内首台(套)产品奖项
阿里云PolarDB数据库管理软件(分布式版)荣获「2024年度国内首版次软件」称号,并跻身《2024年度浙江省首台(套)推广应用典型案例》。
|
8月前
|
SQL 存储 关系型数据库
第二篇:关系型数据库的核心概念与 SQL 基础
本篇内容深入浅出地讲解了关系型数据库的核心概念与SQL基础,适合有一定计算机基础的学习者。文章涵盖数据库的基本操作(CRUD)、数据类型、表的创建与管理等内容,并通过实例解析SELECT、INSERT、UPDATE、DELETE等语句的用法。此外,还推荐了多种学习资源与实践建议,帮助读者巩固知识。学完后,你将掌握基础数据库操作,为后续高级学习铺平道路。
549 1
|
11月前
|
SQL 关系型数据库 分布式数据库
利用 PolarDB PG 版向量化引擎,加速复杂 SQL 查询!完成任务领发财新年抱枕!
利用 PolarDB PG 版向量化引擎,加速复杂 SQL 查询!完成任务领发财新年抱枕!
353 14
|
11月前
|
存储 关系型数据库 分布式数据库
PolarDB开源数据库进阶课3 共享存储在线扩容
本文继续探讨穷鬼玩PolarDB RAC一写多读集群系列,介绍如何在线扩容共享存储。实验环境依赖《在Docker容器中用loop设备模拟共享存储》搭建。主要步骤包括:1) 扩容虚拟磁盘;2) 刷新loop设备容量;3) 使用PFS工具进行文件系统扩容;4) 更新数据库实例以识别新空间。通过这些步骤,成功将共享存储从20GB扩容至30GB,并确保所有节点都能使用新的存储空间。
239 1
|
并行计算 关系型数据库 分布式数据库
朗坤智慧科技「LiEMS企业管理信息系统」通过PolarDB产品生态集成认证!
近日,朗坤智慧科技股份有限公司「LiEMS企业管理信息系统软件」通过PolarDB产品生态集成认证!
|
Cloud Native 关系型数据库 大数据
定川信息「川立方数治平台」通过PolarDB产品生态集成认证!
杭州定川信息技术有限公司「川立方数据治理一体化智能平台」通过PolarDB产品生态集成认证!
|
9月前
|
关系型数据库 分布式数据库 数据库
一库多能:阿里云PolarDB三大引擎、四种输出形态,覆盖企业数据库全场景
PolarDB是阿里云自研的新一代云原生数据库,提供极致弹性、高性能和海量存储。它包含三个版本:PolarDB-M(兼容MySQL)、PolarDB-PG(兼容PostgreSQL及Oracle语法)和PolarDB-X(分布式数据库)。支持公有云、专有云、DBStack及轻量版等多种形态,满足不同场景需求。2021年,PolarDB-PG与PolarDB-X开源,内核与商业版一致,推动国产数据库生态发展,同时兼容主流国产操作系统与芯片,获得权威安全认证。

热门文章

最新文章