PostgreSQL的window函数应用整理

本文转载自:http://my.oschina.net/Kenyon/blog/79543

PG在8.4以后版本中添加了一些Window Function功能,下面简单介绍
A window function performs a calculation across a set of table rows that are somehow related to the current row. This is comparable to the type of calculation that can be done with an aggregate function. But unlike regular aggregate functions,use of a window function does not cause rows to become grouped into a single output row — the rows retain their separate identities. Behind the scenes,the window function is able to access more than just the current row of the query result.
Window Functions in SQL is an OLAP functionality that provides ranking,cumulative computation,and partitioning aggregation. Many commercial RDMBS such like Oracle,MS SQL Server and DB2 have implemented part of this specification,while open source RDMBS including PostgreSQL,MySQL and Firebird doesn’t yet. To implement this functionality on PostgreSQL not only helps many users move from those RDBMS to PostgreSQL but encourages OLAP applications such as BI (Business Inteligence) to analyze large data set. This specification is defined first in SQL:2003,and improved in SQL:2008
简言之,聚合函数返回的各个分组的结果,窗口函数则为每一行返回结果,示例如下:
1.建示例表,初始化数据

DROP TABLE IF EXISTS empsalary;
CREATE TABLE empsalary( depname varchar,empno bigint,salary int,enroll_date date );
INSERT INTO empsalary VALUES('develop',10,5200,'2007/08/01');
INSERT INTO empsalary VALUES('sales',1,5000,'2006/10/01');
INSERT INTO empsalary VALUES('personnel',5,3500,'2007/12/10');
INSERT INTO empsalary VALUES('sales',4,4800,'2007/08/08');
INSERT INTO empsalary VALUES('sales',6,5500,'2007/01/02');
INSERT INTO empsalary VALUES('personnel',2,3900,'2006/12/23');
INSERT INTO empsalary VALUES('develop',7,4200,'2008/01/01');
INSERT INTO empsalary VALUES('develop',9,4500,'2008/01/01');
INSERT INTO empsalary VALUES('sales',3,'2007/08/01');
INSERT INTO empsalary VALUES('develop',8,6000,'2006/10/01');
INSERT INTO empsalary VALUES('develop',11,'2007/08/15');

postgres=# select * from empsalary ;
  depname  | empno | salary | enroll_date 
-----------+-------+--------+-------------
 develop   |    10 |   5200 | 2007-08-01
 sales     |     1 |   5000 | 2006-10-01
 personnel |     5 |   3500 | 2007-12-10
 sales     |     4 |   4800 | 2007-08-08
 sales     |     6 |   5500 | 2007-01-02
 personnel |     2 |   3900 | 2006-12-23
 develop   |     7 |   4200 | 2008-01-01
 develop   |     9 |   4500 | 2008-01-01
 sales     |     3 |   4800 | 2007-08-01
 develop   |     8 |   6000 | 2006-10-01
 develop   |    11 |   5200 | 2007-08-15
(11 rows)

2.统计示例
a.统计各部门的总薪水,平均薪水和部门的详细情况

postgres=# select sum(salary) OVER (PARTITION BY depname),avg(salary) OVER (PARTITION BY depname),* from empsalary;
  sum  | avg | depname | empno | salary | enroll_date 
-------+-----------------------+-----------+-------+--------+-------------
 25100 | 5020.0000000000000000 | develop | 10 | 5200 | 2007-08-01
 25100 | 5020.0000000000000000 | develop | 7 | 4200 | 2008-01-01
 25100 | 5020.0000000000000000 | develop | 9 | 4500 | 2008-01-01
 25100 | 5020.0000000000000000 | develop | 8 | 6000 | 2006-10-01
 25100 | 5020.0000000000000000 | develop | 11 | 5200 | 2007-08-15
  7400 | 3700.0000000000000000 | personnel | 2 | 3900 | 2006-12-23
  7400 | 3700.0000000000000000 | personnel | 5 | 3500 | 2007-12-10
 20100 | 5025.0000000000000000 | sales | 3 | 4800 | 2007-08-01
 20100 | 5025.0000000000000000 | sales | 1 | 5000 | 2006-10-01
 20100 | 5025.0000000000000000 | sales | 4 | 4800 | 2007-08-08
 20100 | 5025.0000000000000000 | sales | 6 | 5500 | 2007-01-02
(11 rows)

b.统计人员在所在部门的薪水排名情况

postgres=# select rank() OVER (PARTITION BY depname ORDER BY salary),* from empsalary;
 rank | depname | empno | salary | enroll_date 
------+-----------+-------+--------+-------------
    1 | develop | 7 | 4200 | 2008-01-01
    2 | develop | 9 | 4500 | 2008-01-01
    3 | develop | 10 | 5200 | 2007-08-01
    3 | develop | 11 | 5200 | 2007-08-15
    5 | develop | 8 | 6000 | 2006-10-01
    1 | personnel | 5 | 3500 | 2007-12-10
    2 | personnel | 2 | 3900 | 2006-12-23
    1 | sales | 4 | 4800 | 2007-08-08
    1 | sales | 3 | 4800 | 2007-08-01
    3 | sales | 1 | 5000 | 2006-10-01
    4 | sales | 6 | 5500 | 2007-01-02
(11 rows)

3.一个有趣的例子 注意使用order by,结果会两样

create table foo(a int,b int) ;
insert into foo values (1,1);
insert into foo values (1,1);
insert into foo values (2,1);
insert into foo values (4,1);
insert into foo values (5,1);
insert into foo values (11,3);
insert into foo values (12,3);
insert into foo values (22,3);
insert into foo values (16,3);

postgres=# select sum(a) over (partition by b),a,b from foo;
 sum | a  | b 
-----+----+---
  19 |  1 | 1
  19 |  1 | 1
  19 |  2 | 1
  19 |  4 | 1
  19 |  2 | 1
  19 |  4 | 1
  19 |  5 | 1
  93 | 11 | 3
  93 | 12 | 3
  93 | 22 | 3
  93 | 16 | 3
  93 | 16 | 3
  93 | 16 | 3
(13 rows)

postgres=# select sum(a) over (partition by b order by a),b from foo;
 sum | a  | b 
-----+----+---
   2 |  1 | 1
   2 |  1 | 1
   6 |  2 | 1
   6 |  2 | 1
  14 |  4 | 1
  14 |  4 | 1
  19 |  5 | 1
  11 | 11 | 3
  23 | 12 | 3
  71 | 16 | 3
  71 | 16 | 3
  71 | 16 | 3
  93 | 22 | 3
(13 rows)

postgres=# select a,b,sum(a) over (partition by b order by a ROWS postgres(# BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) from foo;
 a  | b | sum 
----+---+-----
  1 | 1 |  19
  1 | 1 |  19
  2 | 1 |  19
  2 | 1 |  19
  4 | 1 |  19
  4 | 1 |  19
  5 | 1 |  19
 11 | 3 |  93
 12 | 3 |  93
 16 | 3 |  93
 16 | 3 |  93
 16 | 3 |  93
 22 | 3 |  93
(13 rows)

官网中的解释是: By default,if ORDER BY is supplied then the frame consists of all rows from the start of the partition up through the current row,plus any following rows that are equal to the current row according to the ORDER BY clause. When ORDER BY is omitted the default frame consists of all rows in the partition.
默认情况下,带了order by 参数会从分组的起始值开始一直叠加,直到当前值为止,当忽略order by 参数则会计算分组中所有值的和。

4.其他的窗口函数
row_number(): 从当前开始,不间断,如1,2,3,4,5,6
rank() :从当前开始,会间断,如1,2,2,4,5,6
dense_rank():从当前开始不间断,但会重复,如1,2,2,3,4,5
percent_rank():从当前开始,计算在分组中的比例,如0,0.25,0.25,0.75,1,0,1 从0-1不断地循环
cume_dist():当前行的排序除以分组的数量,如分组有4行,则值为0.25,0.5,0.75,1
ntile(num_buckets integer):从1到当前值,除以分组的的数量,尽可能使分布平均
lag(value any [,offset integer [,default any ]]):偏移量函数,取滞后值,如lag(column_name,2,0)表示字段偏移量为2,没有则用default值代替,这里是0,不写默认是null
lead(value any [,default any ]]):偏移量函数,取提前值,类上
first_value(value any):返回窗口框架中的第一个值
last_value(value any):返回窗口框架中的最后一个值
nth_value(value any,nth integer):返回窗口框架中的指定值,如nth_value(salary,2),则表示返回字段salary的第二个窗口函数值

5.其他窗口函数示例

postgres=# select row_number() over (partition by depname order by salary desc),* from empsalary;
 row_number | depname | empno | salary | enroll_date 
------------+-----------+-------+--------+-------------
          1 | develop | 8 | 6000 | 2006-10-01
          2 | develop | 10 | 5200 | 2007-08-01
          3 | develop | 11 | 5200 | 2007-08-15
          4 | develop | 9 | 4500 | 2008-01-01
          5 | develop | 7 | 4200 | 2008-01-01
          1 | personnel | 2 | 3900 | 2006-12-23
          2 | personnel | 5 | 3500 | 2007-12-10
          1 | sales | 6 | 5500 | 2007-01-02
          2 | sales | 1 | 5000 | 2006-10-01
          3 | sales | 3 | 4800 | 2007-08-01
          4 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select rank() over(partition by depname order by salary desc),* from empsalary;
 rank | depname | empno | salary | enroll_date 
------+-----------+-------+--------+-------------
    1 | develop | 8 | 6000 | 2006-10-01
    2 | develop | 10 | 5200 | 2007-08-01
    2 | develop | 11 | 5200 | 2007-08-15
    4 | develop | 9 | 4500 | 2008-01-01
    5 | develop | 7 | 4200 | 2008-01-01
    1 | personnel | 2 | 3900 | 2006-12-23
    2 | personnel | 5 | 3500 | 2007-12-10
    1 | sales | 6 | 5500 | 2007-01-02
    2 | sales | 1 | 5000 | 2006-10-01
    3 | sales | 3 | 4800 | 2007-08-01
    3 | sales | 4 | 4800 | 2007-08-08
(11 rows)


postgres=# select dense_rank() over(partition by depname order by salary desc),* from empsalary;
 dense_rank | depname | empno | salary | enroll_date 
------------+-----------+-------+--------+-------------
          1 | develop | 8 | 6000 | 2006-10-01
          2 | develop | 10 | 5200 | 2007-08-01
          2 | develop | 11 | 5200 | 2007-08-15
          3 | develop | 9 | 4500 | 2008-01-01
          4 | develop | 7 | 4200 | 2008-01-01
          1 | personnel | 2 | 3900 | 2006-12-23
          2 | personnel | 5 | 3500 | 2007-12-10
          1 | sales | 6 | 5500 | 2007-01-02
          2 | sales | 1 | 5000 | 2006-10-01
          3 | sales | 3 | 4800 | 2007-08-01
          3 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select percent_rank() over(partition by depname order by salary desc),* from empsalary;
   percent_rank    | depname | empno | salary | enroll_date 
-------------------+-----------+-------+--------+-------------
                 0 | develop | 8 | 6000 | 2006-10-01
              0.25 | develop | 10 | 5200 | 2007-08-01
              0.25 | develop | 11 | 5200 | 2007-08-15
              0.75 | develop | 9 | 4500 | 2008-01-01
                 1 | develop | 7 | 4200 | 2008-01-01
                 0 | personnel | 2 | 3900 | 2006-12-23
                 1 | personnel | 5 | 3500 | 2007-12-10
                 0 | sales | 6 | 5500 | 2007-01-02
 0.333333333333333 | sales | 1 | 5000 | 2006-10-01
 0.666666666666667 | sales | 3 | 4800 | 2007-08-01
 0.666666666666667 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select cume_dist()over(partition by depname order by salary desc),* from empsalary;
 cume_dist | depname | empno | salary | enroll_date 
-----------+-----------+-------+--------+-------------
       0.2 | develop | 8 | 6000 | 2006-10-01
       0.6 | develop | 10 | 5200 | 2007-08-01
       0.6 | develop | 11 | 5200 | 2007-08-15
       0.8 | develop | 9 | 4500 | 2008-01-01
         1 | develop | 7 | 4200 | 2008-01-01
       0.5 | personnel | 2 | 3900 | 2006-12-23
         1 | personnel | 5 | 3500 | 2007-12-10
      0.25 | sales | 6 | 5500 | 2007-01-02
       0.5 | sales | 1 | 5000 | 2006-10-01
         1 | sales | 3 | 4800 | 2007-08-01
         1 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select ntile(3)over(partition by depname order by salary desc),* from empsalary;
 ntile | depname | empno | salary | enroll_date 
-------+-----------+-------+--------+-------------
     1 | develop | 8 | 6000 | 2006-10-01
     1 | develop | 10 | 5200 | 2007-08-01
     2 | develop | 11 | 5200 | 2007-08-15
     2 | develop | 9 | 4500 | 2008-01-01
     3 | develop | 7 | 4200 | 2008-01-01
     1 | personnel | 2 | 3900 | 2006-12-23
     2 | personnel | 5 | 3500 | 2007-12-10
     1 | sales | 6 | 5500 | 2007-01-02
     1 | sales | 1 | 5000 | 2006-10-01
     2 | sales | 3 | 4800 | 2007-08-01
     3 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select lag(salary,null)over(partition by depname order by salary desc),* from empsalary;
 lag  | depname | empno | salary | enroll_date 
------+-----------+-------+--------+-------------
      | develop | 8 | 6000 | 2006-10-01
      | develop | 10 | 5200 | 2007-08-01
 6000 | develop | 11 | 5200 | 2007-08-15
 5200 | develop | 9 | 4500 | 2008-01-01
 5200 | develop | 7 | 4200 | 2008-01-01
      | personnel | 2 | 3900 | 2006-12-23
      | personnel | 5 | 3500 | 2007-12-10
      | sales | 6 | 5500 | 2007-01-02
      | sales | 1 | 5000 | 2006-10-01
 5500 | sales | 3 | 4800 | 2007-08-01
 5000 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select first_value(salary)over(partition by depname order by salary desc),* from empsalary;
 first_value | depname | empno | salary | enroll_date 
-------------+-----------+-------+--------+-------------
        6000 | develop | 8 | 6000 | 2006-10-01
        6000 | develop | 10 | 5200 | 2007-08-01
        6000 | develop | 11 | 5200 | 2007-08-15
        6000 | develop | 9 | 4500 | 2008-01-01
        6000 | develop | 7 | 4200 | 2008-01-01
        3900 | personnel | 2 | 3900 | 2006-12-23
        3900 | personnel | 5 | 3500 | 2007-12-10
        5500 | sales | 6 | 5500 | 2007-01-02
        5500 | sales | 1 | 5000 | 2006-10-01
        5500 | sales | 3 | 4800 | 2007-08-01
        5500 | sales | 4 | 4800 | 2007-08-08
(11 rows) 

postgres=# select last_value(salary)over(partition by depname order by salary desc),* from empsalary;
 last_value | depname | empno | salary | enroll_date 
------------+-----------+-------+--------+-------------
       6000 | develop | 8 | 6000 | 2006-10-01
       5200 | develop | 10 | 5200 | 2007-08-01
       5200 | develop | 11 | 5200 | 2007-08-15
       4500 | develop | 9 | 4500 | 2008-01-01
       4200 | develop | 7 | 4200 | 2008-01-01
       3900 | personnel | 2 | 3900 | 2006-12-23
       3500 | personnel | 5 | 3500 | 2007-12-10
       5500 | sales | 6 | 5500 | 2007-01-02
       5000 | sales | 1 | 5000 | 2006-10-01
       4800 | sales | 3 | 4800 | 2007-08-01
       4800 | sales | 4 | 4800 | 2007-08-08
(11 rows)

postgres=# select last_value(aa.salary)over(partition by aa.depname),* from 
(select depname,empno,salary,enroll_date from empsalary order by depname,salary ) aa;
 last_value | depname | empno | salary | enroll_date 
------------+-----------+-------+--------+-------------
       6000 | develop | 7 | 4200 | 2008-01-01
       6000 | develop | 9 | 4500 | 2008-01-01
       6000 | develop | 10 | 5200 | 2007-08-01
       6000 | develop | 11 | 5200 | 2007-08-15
       6000 | develop | 8 | 6000 | 2006-10-01
       3900 | personnel | 5 | 3500 | 2007-12-10
       3900 | personnel | 2 | 3900 | 2006-12-23
       5500 | sales | 4 | 4800 | 2007-08-08
       5500 | sales | 3 | 4800 | 2007-08-01
       5500 | sales | 1 | 5000 | 2006-10-01
       5500 | sales | 6 | 5500 | 2007-01-02
(11 rows)

postgres=# select nth_value(salary,2)over(partition by depname order by salary desc),* from empsalary;
 nth_value | depname | empno | salary | enroll_date 
-----------+-----------+-------+--------+-------------
           | develop | 8 | 6000 | 2006-10-01
      5200 | develop | 10 | 5200 | 2007-08-01
      5200 | develop | 11 | 5200 | 2007-08-15
      5200 | develop | 9 | 4500 | 2008-01-01
      5200 | develop | 7 | 4200 | 2008-01-01
           | personnel | 2 | 3900 | 2006-12-23
      3500 | personnel | 5 | 3500 | 2007-12-10
           | sales | 6 | 5500 | 2007-01-02
      5000 | sales | 1 | 5000 | 2006-10-01
      5000 | sales | 3 | 4800 | 2007-08-01
      5000 | sales | 4 | 4800 | 2007-08-08
(11 rows)
当一个查询涉及多个窗口函数的时候,可以用别名的办法来使用,更简单:
postgres=# select sum(salary)over w,avg(salary) over w,* from empsalary window w as (partition by depname order by salary desc);
  sum  | avg | depname | empno | salary | enroll_date 
-------+-----------------------+-----------+-------+--------+-------------
  6000 | 6000.0000000000000000 | develop | 8 | 6000 | 2006-10-01
 16400 | 5466.6666666666666667 | develop | 10 | 5200 | 2007-08-01
 16400 | 5466.6666666666666667 | develop | 11 | 5200 | 2007-08-15
 20900 | 5225.0000000000000000 | develop | 9 | 4500 | 2008-01-01
 25100 | 5020.0000000000000000 | develop | 7 | 4200 | 2008-01-01
  3900 | 3900.0000000000000000 | personnel | 2 | 3900 | 2006-12-23
  7400 | 3700.0000000000000000 | personnel | 5 | 3500 | 2007-12-10
  5500 | 5500.0000000000000000 | sales | 6 | 5500 | 2007-01-02
 10500 | 5250.0000000000000000 | sales | 1 | 5000 | 2006-10-01
 20100 | 5025.0000000000000000 | sales | 3 | 4800 | 2007-08-01
 20100 | 5025.0000000000000000 | sales | 4 | 4800 | 2007-08-08
(11 rows)

这个写法和下面的是一样的,不过更简单
SELECT sum(salary) OVER (PARTITION BY depname ORDER BY salary DESC),avg(salary) OVER (PARTITION BY depname ORDER BY salary DESC),* FROM empsalary;

上面给了两个last_value的示例,但是第一种写法是没有问题的,虽然并不能达到返回窗口最后一个值的效果,而且first_value没有这种问题的,其实,参考前面的官网提醒,一样可得出类似的结论:都是order by 惹的祸
官网中的解释是: By default,plus any following rows that are equal to the current row according to the ORDER BY clause. When ORDER BY is omitted the default frame consists of all rows in the partition.
默认情况下,带了order by 参数会从分组的起始值开始一直叠加,直到当前值为止,当忽略order by 参数则会计算分组中所有值的和。

感谢joan_he@189.cn的提醒和digoal的解释。

参考文档:http://umitanuki.net/pgsql/wfv08/design.html

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


文章浏览阅读601次。Oracle的数据导入导出是一项基本的技能,但是对于懂数据库却不熟悉Oracle的同学可能会有一定的障碍。正好在最近的一个项目中碰到了这样一个任务,于是研究了一下Oracle的数据导入导出,在这里跟大家分享一下。......_oracle 迁移方法 对比
文章浏览阅读553次。开头还是介绍一下群,如果感兴趣polardb ,mongodb ,mysql ,postgresql ,redis 等有问题,有需求都可以加群群内有各大数据库行业大咖,CTO,可以解决你的问题。加群请联系 liuaustin3 ,在新加的朋友会分到2群(共700多人左右 1 + 2)。最近我们在使用MYSQL 8 的情况下(8.025)在数据库运行中出现一个问题 参数prefer_order_i..._mysql prefer_ordering_index
文章浏览阅读3.5k次,点赞3次,收藏7次。折腾了两个小时多才成功连上,在这分享一下我的经验,也仅仅是经验分享,有不足的地方欢迎大家在评论区补充交流。_navicat连接opengauss
文章浏览阅读2.7k次。JSON 代表 JavaScript Object Notation。它是一种开放标准格式,将数据组织成中详述的键/值对和数组。_postgresql json
文章浏览阅读2.9k次,点赞2次,收藏6次。navicat 连接postgresql 注:navicat老版本可能报错。1.在springboot中引入我们需要的依赖以及相应版本。用代码生成器生成代码后,即可进行增删改查(略)安装好postgresql 略。更改配置信息(注释中有)_mybatisplus postgresql
文章浏览阅读1.4k次。postgre进阶sql,包含分组排序、JSON解析、修改、删除、更新、强制踢出数据库所有使用用户、连表更新与删除、获取今年第一天、获取近12个月的年月、锁表处理、系统表使用(查询所有表和字段及注释、查询表占用空间)、指定数据库查找模式search_path、postgre备份及还原_pgsql分组取每组第一条
文章浏览阅读3.3k次。上一篇我们学习了日志清理,日志清理虽然解决了日志膨胀的问题,但就无法再恢复检查点之前的一致性状态。因此,我们还需要日志归档,pg的日志归档原理和Oracle类似,不过归档命令需要自己配置。以下代码在postmaster.c除了开启归档外,还需要保证wal_level不能是MINIMAL状态(因为该状态下有些操作不会记录日志)。在db启动时,会同时检查archive_mode和wal_level。以下代码也在postmaster.c(PostmasterMain函数)。......_postgresql archive_mode
文章浏览阅读3k次。系统:ubuntu22.04.3目的:利用向日葵实现windows远程控制ubuntu。_csdn局域网桌面控制ubuntu
文章浏览阅读1.6k次。表分区是解决一些因单表过大引用的性能问题的方式,比如某张表过大就会造成查询变慢,可能分区是一种解决方案。一般建议当单表大小超过内存就可以考虑表分区了。1,继承式分区,分为触发器(trigger)和规则(rule)两种方式触发器的方式1)创建表CREATE TABLE "public"."track_info_trigger_partition" ( "id" serial, "object_type" int2 NOT NULL DEFAULT 0, "object_name..._pg数据表分区的实现
文章浏览阅读3.3k次。物联网平台开源的有几个,就我晓得的有、、thingskit、JetLink、DG-iot(还有其他开源的,欢迎在评论区留言哦!),然后重点分析了下ThingsBoard、ThingsPanel和JetLink,ThingsBoard和Jetlinks是工程师思维产品,可以更多的通过配置去实现开发的目的,ThingsPanel是业务人员思路产品,或者开发或者用,避免了复杂的配置带来的较高学习门槛。ThingsBoard和Jetlinks是Java技术体系的,ThingsPanel是PHP开发的。_jetlinks和thingsboard
文章浏览阅读3.8k次。PostgreSQL 数据类型转换_pgsql数字转字符串
文章浏览阅读7k次,点赞3次,收藏14次。在做数据统计页面时,总会遇到统计某段时间内,每天、每月、每年的数据视图(柱状图、折线图等)。这些统计数据一眼看过去也简单呀,不就是按照时间周期(天、月、年)对统计数据进行分个组就完了嘛?但是会有一个问题,简单的写个sql对周期分组,获取到的统计数据是缺失的,即没有数据的那天,整条记录也都没有了。如下图需求:以当前月份(2023年2月)为起点,往后倒推一年,查询之前一年里每个月的统计数据。可见图中的数据其实是缺少的,这条sql只查询到了有数据的月份(23年的1月、2月,22年的12月)_如何用一条sql查出按年按月按天的汇总
文章浏览阅读3.8k次,点赞66次,收藏51次。PostgreSQL全球开发小组与2022年10月13日,宣布发布PostgreSQL15,这是世界上最先进的开源数据库的最新版本_mysql8 postgresql15
文章浏览阅读1.3k次。上文介绍了磁盘管理器中VFD的实现原理,本篇将从上层角度讲解磁盘管理器的工作细节。_smgrrelationdata
文章浏览阅读1.1k次。PostgreSQL设置中文语言界面和局域网访问_postgressql汉化
文章浏览阅读4.2k次。PostgreSQL 修改数据存储路径_如何设置postgresql 数据目录
文章浏览阅读4.7k次。在项目中用到了多数据源,在连接postgres数据库时,项目启动报错,说数据库连接错误,说dual不存在,网上好多教程都是说数据库查询的时候的大小写问题,而这个仅仅是连接,咋鞥却处理方法是修改application-dev.yml中的配置文件.项目中的druid参数是这样的:确实在配置文件中有个查询语句。_relation "dual" does not exist
文章浏览阅读4.9k次。PostgreSQL是一款强大的关系型数据库,但在实际使用过程中,许多用户经常会遇到慢SQL的问题。这些问题不仅会降低数据库性能,还会直接影响业务流程和用户体验。因此,本文将会深入分析PostgreSQL慢SQL的原因和优化方案,帮助用户更好地利用这个优秀的数据库系统。无论你是初学者还是专业开发者,本文都将为你提供实用的技巧和方法,让你的PostgreSQL数据库始终保持高效快速。_postgresql数据库优化
文章浏览阅读1.6k次。Linux配置postgresql开机自启_linux 启动pgsql
文章浏览阅读2k次。本篇介绍如何在centos7系统搭建一个postgresql主备集群实现最近的HA(高可用)架构。后续更高级的HA模式都是基于这个最基本的主备搭建。_postgresql主备