postgresql - Postgres : strange behavior with optimistic locking-6ren

postgresql - Postgres : strange behavior with optimistic locking

转载作者：行者123 更新时间：2023-11-29 13:20:18

我正在调试使用 JPA/Hibernate 和 Postgres (9.6.2) 的 Java 应用程序的奇怪行为。

应用程序有 3 个实体:User、Country、UserEvent。

Hibernate 将其映射到 4 个表:users、countries、userevent、hibernate_sequences。

用户实体有版本列(@Version)和乐观锁定的主题。 @GeneratedValue(strategy = GenerationType.TABLE) 为其主键“id”。用户表将接收最多的读写次数(最流行的表)。

我创建了几个压力测试来模拟高负载，并在我运行它们时注意到 Postgres 日志中的以下错误(请注意导致它的更新查询):

ERROR:  deadlock detected
DETAIL:  Process 46758 waits for ShareLock on transaction 1580660; blocked by process 46759.
  Process 46759 waits for AccessExclusiveLock on tuple (97,26) of relation 17353 of database 16385; blocked by process 46758.

  Process 46758: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
  Process 46759: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19

  HINT:  See server log for query details.
  CONTEXT:  while updating tuple (97,26) in relation "users"

我明白Postgres有shared和exclusive；行、表或索引级别的锁。以错误的顺序在相同的对象上获取它们可能会导致死锁。

但对于这种特殊情况，为什么我会遇到乐观锁定的死锁？在这种情况下，我希望一笔交易成功，一笔交易返回 0 UPDATE。

表格、FK及其索引说明如下:

##################################################################################################

                                        Table "public.users"
      Column       |            Type             | Modifiers | Storage  | Stats target | Description 
-------------------+-----------------------------+-----------+----------+--------------+-------------
 id                | bigint                      | not null  | plain    |              | 
 confirmationstate | character varying(20)       | not null  | extended |              | 
 created           | timestamp without time zone | not null  | plain    |              | 
 dateofbirth       | date                        | not null  | plain    |              | 
 email             | character varying(255)      | not null  | extended |              | 
 firstname         | character varying(100)      | not null  | extended |              | 
 gender            | character varying(10)       | not null  | extended |              | 
 lastname          | character varying(100)      | not null  | extended |              | 
 lastusedlocale    | character varying(5)        |           | extended |              | 
 middlename        | character varying(100)      |           | extended |              | 
 passwordhash      | bytea                       | not null  | extended |              | 
 passwordsalt      | bytea                       | not null  | extended |              | 
 phone             | character varying(50)       |           | extended |              | 
 role              | character varying(50)       | not null  | extended |              | 
 signinstate       | character varying(20)       | not null  | extended |              | 
 updated           | timestamp without time zone | not null  | plain    |              | 
 username          | character varying(255)      |           | extended |              | 
 version           | bigint                      |           | plain    |              | 
 country_iso       | character varying(2)        |           | extended |              | 
Indexes:
    "users_pkey" PRIMARY KEY, btree (id)
    "email_idx" UNIQUE CONSTRAINT, btree (email)
    "username_idx" UNIQUE CONSTRAINT, btree (username)
    "firstname_idx" btree (firstname)
    "lastname_idx" btree (lastname)
    "phone_idx" btree (phone)
Foreign-key constraints:
    "fk_ghgfskd1hgobolp0fh20i6h14" FOREIGN KEY (country_iso) REFERENCES countries(iso)
Referenced by:
    TABLE "userevents" CONSTRAINT "fk_69tm2wh9hkakap0uyjw41c61h" FOREIGN KEY (targetuser_id) REFERENCES users(id)
    TABLE "userevents" CONSTRAINT "fk_nov1tso5k93h4m88unjy4f2kl" FOREIGN KEY (user_id) REFERENCES users(id)

##################################################################################################

                                Table "public.countries"
   Column   |          Type          | Modifiers | Storage  | Stats target | Description 
------------+------------------------+-----------+----------+--------------+-------------
 iso        | character varying(2)   | not null  | extended |              | 
 iso3       | character varying(3)   |           | extended |              | 
 name       | character varying(80)  |           | extended |              | 
 nativename | character varying(150) |           | extended |              | 
 numcode    | integer                |           | plain    |              | 
 phonecode  | integer                | not null  | plain    |              | 
Indexes:
    "countries_pkey" PRIMARY KEY, btree (iso)
    "iso3_idx" UNIQUE CONSTRAINT, btree (iso3)
    "nativename_idx" btree (nativename)
Referenced by:
    TABLE "users" CONSTRAINT "fk_ghgfskd1hgobolp0fh20i6h14" FOREIGN KEY (country_iso) REFERENCES countries(iso)    

##################################################################################################

                                    Table "public.userevents"
    Column     |            Type             | Modifiers | Storage  | Stats target | Description 
---------------+-----------------------------+-----------+----------+--------------+-------------
 id            | bigint                      | not null  | plain    |              | 
 data          | bytea                       |           | extended |              | 
 ip            | character varying(255)      | not null  | extended |              | 
 time          | timestamp without time zone | not null  | plain    |              | 
 type          | character varying(15)       | not null  | extended |              | 
 url           | character varying(2000)     |           | extended |              | 
 targetuser_id | bigint                      |           | plain    |              | 
 user_id       | bigint                      | not null  | plain    |              | 
Indexes:
    "userevents_pkey" PRIMARY KEY, btree (id)
    "usertypetime_idx" btree (user_id, type, "time")
Foreign-key constraints:
    "fk_69tm2wh9hkakap0uyjw41c61h" FOREIGN KEY (targetuser_id) REFERENCES users(id)
    "fk_nov1tso5k93h4m88unjy4f2kl" FOREIGN KEY (user_id) REFERENCES users(id)

##################################################################################################    

Table "public.hibernate_sequences"
         Column         |          Type          | Modifiers | Storage  | Stats target | Description 
------------------------+------------------------+-----------+----------+--------------+-------------
 sequence_name          | character varying(255) |           | extended |              | 
 sequence_next_hi_value | integer                |           | plain    |              | 

##################################################################################################

编辑 1:

先生。 pozs 建议查看循环 FK 的现有问题，并提供有关交易中发生的情况的更多详细信息。我在此架构中没有循环 FK，因此我在 Postgres 中设置了日志记录并尝试隔离问题。

这是导致死锁的 2 个进程的所有语句的完整日志。

进程 1 日志:

2017-04-11 12:41:31 PDT      73842 LOG:  00000: execute S_2: BEGIN    
2017-04-11 12:41:31 PDT      73842 LOG:  00000: execute S_3: select user0_.id as id1_2_0_, user0_.confirmationState as confirma2_2_0_, user0_.country_iso as country19_2_0_, user0_.created as created3_2_0_, user0_.dateOfBirth as dateOfBi4_2_0_, user0_.email as email5_2_0_, user0_.firstName as firstNam6_2_0_, user0_.gender as gender7_2_0_, user0_.lastName as lastName8_2_0_, user0_.lastUsedLocale as lastUsed9_2_0_, user0_.middleName as middleN10_2_0_, user0_.passwordHash as passwor11_2_0_, user0_.passwordSalt as passwor12_2_0_, user0_.phone as phone13_2_0_, user0_.role as role14_2_0_, user0_.signInState as signInS15_2_0_, user0_.updated as updated16_2_0_, user0_.username as usernam17_2_0_, user0_.version as version18_2_0_, country1_.iso as iso1_0_1_, country1_.iso3 as iso2_0_1_, country1_.name as name3_0_1_, country1_.nativeName as nativeNa4_0_1_, country1_.numCode as numCode5_0_1_, country1_.phoneCode as phoneCod6_0_1_ from users user0_ left outer join countries country1_ on user0_.country_iso=country1_.iso where user0_.id=$1
2017-04-11 12:41:31 PDT      73842 DETAIL:  parameters: $1 = '10'
2017-04-11 12:41:31 PDT      73842 LOG:  00000: execute S_10: select country0_.iso as iso1_0_, country0_.iso3 as iso2_0_, country0_.name as name3_0_, country0_.nativeName as nativeNa4_0_, country0_.numCode as numCode5_0_, country0_.phoneCode as phoneCod6_0_ from countries country0_ order by country0_.nativeName, country0_.name
2017-04-11 12:41:31 PDT      73842 LOG:  00000: execute S_4: insert into userEvents (data, ip, targetUser_id, time, type, url, user_id, id) values ($1, $2, $3, $4, $5, $6, $7, $8)
2017-04-11 12:41:31 PDT      73842 DETAIL:  parameters: $1 = '\x04545...LONG_BINARY_DATA...d', $2 = '192.168.1.2', $3 = '10', $4 = '2017-04-11 19:41:31.268', $5 = 'UPDATE', $6 = 'http://example.org', $7 = '10', $8 = '201243'
2017-04-11 12:41:31 PDT      73842 LOG:  00000: execute S_7: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:31 PDT      73842 DETAIL:  parameters: $1 = 'CONFIRMED', $2 = 'IS', $3 = '1984-10-10', $4 = 'email-527785869@example.org', $5 = 's7w7j5cdm1bg', $6 = 'FEMALE', $7 = 'Terrier9', $8 = 'en', $9 = 'Russel', $10 = '\x64..6439', $11 = '\x33...3836', $12 = '+16509876945', $13 = 'USER', $14 = 'ENABLED', $15 = '2017-04-11 19:41:31.268', $16 = 'demouser9', $17 = '547', $18 = '10', $19 = '546'
2017-04-11 12:41:32 PDT      73842 LOG:  00000: process 73842 detected deadlock while waiting for ExclusiveLock on tuple (206,43) of relation 17992 of database 16385 after 1000.114 ms
2017-04-11 12:41:32 PDT      73842 DETAIL:  Process holding the lock: 73817. Wait queue: .
2017-04-11 12:41:32 PDT      73842 LOCATION:  ProcSleep, proc.c:1415
2017-04-11 12:41:32 PDT      73842 STATEMENT:  update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:32 PDT      73842 ERROR:  40P01: deadlock detected
2017-04-11 12:41:32 PDT      73842 DETAIL:  Process 73842 waits for ExclusiveLock on tuple (206,43) of relation 17992 of database 16385; blocked by process 73817.
        Process 73817 waits for ShareLock on transaction 2716972; blocked by process 73842.
        Process 73842: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:32 PDT      73842 HINT:  See server log for query details.
2017-04-11 12:41:32 PDT      73842 LOCATION:  DeadLockReport, deadlock.c:1140
2017-04-11 12:41:32 PDT      73842 STATEMENT:  update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:32 PDT      73842 ERROR:  25P02: current transaction is aborted, commands ignored until end of transaction block
2017-04-11 12:41:32 PDT      73842 LOCATION:  exec_parse_message, postgres.c:1303
2017-04-11 12:41:32 PDT      73842 STATEMENT:  SELECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS TABLE_NAME,  CASE n.nspname ~ '^pg_' OR n.nspname = 'information_schema'  WHEN true THEN CASE  WHEN n.nspname = 'pg_catalog' OR n.nspname = 'information_schema' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TABLE'   WHEN 'v' THEN 'SYSTEM VIEW'   WHEN 'i' THEN 'SYSTEM INDEX'   ELSE NULL   END  WHEN n.nspname = 'pg_toast' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TOAST TABLE'   WHEN 'i' THEN 'SYSTEM TOAST INDEX'   ELSE NULL   END  ELSE CASE c.relkind   WHEN 'r' THEN 'TEMPORARY TABLE'   WHEN 'i' THEN 'TEMPORARY INDEX'   WHEN 'S' THEN 'TEMPORARY SEQUENCE'   WHEN 'v' THEN 'TEMPORARY VIEW'   ELSE NULL   END  END  WHEN false THEN CASE c.relkind  WHEN 'r' THEN 'TABLE'  WHEN 'i' THEN 'INDEX'  WHEN 'S' THEN 'SEQUENCE'  WHEN 'v' THEN 'VIEW'  WHEN 'c' THEN 'TYPE'  WHEN 'f' THEN 'FOREIGN TABLE'  WHEN 'm' THEN 'MATERIALIZED VIEW'  ELSE NULL  END  ELSE NULL  END  AS TABLE_TYPE, d.description AS REMARKS  FROM pg_catalog.pg_namespace n, pg_catalog.pg_class c  LEFT JOIN pg_catalog.pg_description d ON (c.oid = d.objoid AND d.objsubid = 0)  LEFT JOIN pg_catalog.pg_class dc ON (d.classoid=dc.oid AND dc.relname='pg_class')  LEFT JOIN pg_catalog.pg_namespace dn ON (dn.oid=dc.relnamespace AND dn.nspname='pg_catalog')  WHERE c.relnamespace = n.oid  AND c.relname LIKE 'PROBABLYNOT' AND (false  OR ( c.relkind = 'r' AND n.nspname !~ '^pg_' AND n.nspname <> 'information_schema' ) )  ORDER BY TABLE_TYPE,TABLE_SCHEM,TABLE_NAME 
2017-04-11 12:41:32 PDT      73842 LOG:  00000: execute S_11: ROLLBACK

进程 2 日志:

2017-04-11 12:41:31 PDT      73817 LOG:  00000: execute S_2: BEGIN
2017-04-11 12:41:31 PDT      73817 LOG:  00000: execute S_3: select user0_.id as id1_2_0_, user0_.confirmationState as confirma2_2_0_, user0_.country_iso as country19_2_0_, user0_.created as created3_2_0_, user0_.dateOfBirth as dateOfBi4_2_0_, user0_.email as email5_2_0_, user0_.firstName as firstNam6_2_0_, user0_.gender as gender7_2_0_, user0_.lastName as lastName8_2_0_, user0_.lastUsedLocale as lastUsed9_2_0_, user0_.middleName as middleN10_2_0_, user0_.passwordHash as passwor11_2_0_, user0_.passwordSalt as passwor12_2_0_, user0_.phone as phone13_2_0_, user0_.role as role14_2_0_, user0_.signInState as signInS15_2_0_, user0_.updated as updated16_2_0_, user0_.username as usernam17_2_0_, user0_.version as version18_2_0_, country1_.iso as iso1_0_1_, country1_.iso3 as iso2_0_1_, country1_.name as name3_0_1_, country1_.nativeName as nativeNa4_0_1_, country1_.numCode as numCode5_0_1_, country1_.phoneCode as phoneCod6_0_1_ from users user0_ left outer join countries country1_ on user0_.country_iso=country1_.iso where user0_.id=$1
2017-04-11 12:41:31 PDT      73817 DETAIL:  parameters: $1 = '10'
2017-04-11 12:41:31 PDT      73817 LOG:  00000: execute S_6: select country0_.iso as iso1_0_0_, country0_.iso3 as iso2_0_0_, country0_.name as name3_0_0_, country0_.nativeName as nativeNa4_0_0_, country0_.numCode as numCode5_0_0_, country0_.phoneCode as phoneCod6_0_0_ from countries country0_ where country0_.iso=$1
2017-04-11 12:41:31 PDT      73817 DETAIL:  parameters: $1 = 'JP'
2017-04-11 12:41:31 PDT      73817      
2017-04-11 12:41:31 PDT      73817 LOG:  00000: execute S_5: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:31 PDT      73817 DETAIL:  parameters: $1 = 'CONFIRMED', $2 = 'JP', $3 = '1984-10-10', $4 = 'email465994020@example.org', $5 = '-1kcg4facio48g', $6 = 'FEMALE', $7 = 'Terrier9', $8 = 'en', $9 = 'Russel', $10 = '\x64656d6f7573657270617373776f726439', $11 = '\x33...3836', $12 = '+16509876905', $13 = 'USER', $14 = 'ENABLED', $15 = '2017-04-11 19:41:31.188', $16 = 'demouser9', $17 = '547', $18 = '10', $19 = '546'
2017-04-11 12:41:32 PDT      73842 DETAIL:  Process holding the lock: 73817. Wait queue: .
2017-04-11 12:41:32 PDT      73842 DETAIL:  Process 73842 waits for ExclusiveLock on tuple (206,43) of relation 17992 of database 16385; blocked by process 73817.
        Process 73817 waits for ShareLock on transaction 2716972; blocked by process 73842.
        Process 73817: update users set confirmationState=$1, country_iso=$2, dateOfBirth=$3, email=$4, firstName=$5, gender=$6, lastName=$7, lastUsedLocale=$8, middleName=$9, passwordHash=$10, passwordSalt=$11, phone=$12, role=$13, signInState=$14, updated=$15, username=$16, version=$17 where id=$18 and version=$19
2017-04-11 12:41:32 PDT      73817 LOG:  00000: execute S_10: ROLLBACK

进程 1 的流程是:

开始；
SELECT * FROM users WHERE id = 10;
SELECT * FROM countries;//不影响问题
INSERT INTO userEvents (..., user_id, ...) VALUES (..., 10, ...);
UPDATE users SET [..fields to update..] WHERE id = 10 AND version = 546;
提交；

进程 2 的流程是:

开始；
SELECT * FROM users WHERE id = 10;
UPDATE users SET [..fields to update..] WHERE id = 10 AND version = 546;
提交；

是否因为顺序获取FK (userEvents.user_id) 的排他锁以进行插入，然后获取UPDATE 的排他锁(users.id = 10) 在第一个事务中，(users.id = 10) 和(userEvents.user_id) 在第二个更新中em>？

因为当我在“INSERT INTO userEvents”之前强制“UPDATE users”时，我在高负载下不再看到死锁。

最佳答案

如果两个事务试图同时更新具有相同版本的同一行，那么其中一个将获取该行的锁，而另一个将阻塞。

只要第一个事务处于事件状态，第二个事务就无法决定它是否“获得”了乐观锁。如果第一个事务成功，第二个事务将发现 version 不再匹配，并且将不更新任何内容而返回。但是，如果第一个事务回滚，第二个事务将获取旧版本 上的锁并继续更新。

与此同时，它只需要等待，一旦您有事务等待，就很容易构造死锁场景。

关于postgresql - Postgres : strange behavior with optimistic locking，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/43247757/

文章推荐： postgresql - 在 postgres 中存储和访问相关对象

文章推荐： php - 使用 PDO/PHP 注册不起作用

文章推荐： mysql - 我需要拥有最多视频的类别(max() 不起作用)

java - Strange if 行为的解释
这个问题在这里已经有了答案: How do I compare strings in Java? (23 个回答) 关闭 9 年前。所以我运行了这段代码 String line =
jQuery on() : strange behaviour
此代码适用于我的网站: $(function(){ $('.link-follow-stop').on('click', function(event){ console.lo
java和线程: very strange behaviour
private synchronized Map calculateStanding() { System.out.println("Calculate standing for
Java内存不足错误: Strange behavior
下面的程序 (prog1) 抛出 OutOfMemoryError 错误。确实如此。但如果我在第 5 行(prog2)下方添加 sysout，它不会抛出错误。这种奇怪的行为有什么原因吗？程序1: p
Python "strange"输出
class Foo(object): def __init__(self,x): self.x = x self.is_bar = False def
CSS :after & :before acting very strangely
好的，我有一个设置了高度和宽度的简单 div。前后也设置了高度和宽度。它们都设置为显示为 block ，伪元素的内容为“”。 :before 在内容里面，而不是在它之前。:after 之前有一大堆奇怪
Scala 可变集 : strange behavior
我无法解释 Scala 集合的这种行为。让我们从一些定义开始。 import scala.collection.mutable.Set case class Item(name: String, c
C 结构初始化 : strange way
在阅读我遇到的代码时，结构的以下定义和初始化: // header file struct foo{ char* name; int value; }; //Implementation file s
c - 二进制数 : strange differences between + and |
我正在尝试用 c 操作二进制数。我用下面的最小代码发现了一个奇怪的事情。谁能告诉我“+”和“|”有什么区别这里？谢谢! char next_byte1 = 0b11111111; char next_
德尔福tstream : strange behaviour on create
我是德尔福的新手。在 TStrem 类的文档中，我读到它是一个抽象类。所以我认为当我尝试使用创建它时编译器会出错 stream := TStream.Create(); 为什么不呢？最佳答案 De
delphi - GetAsyncKeyState "strange"行为
我有 2 个简单的表单，Form1 和 Form2 (Delphi 7)。 Form1 打开 Form2，我在那里等待特定的组合键 (Ctrl + F2)。一旦我关闭 Form2 并返回到 Form1
c++ - “Strange”内存泄漏-TCP网络
我有很多建立TCP网络的类-使用boost::asio，使用Packet进行传输。 (Packet的基类是std::vector) 我以为我已经解决了所有可能的内存泄漏，但是后来我在关闭客户端之前只是
sql - 解码语句 : strange behaviour
我对以下声明有一些疑问: SELECT 1 FROM dual WHERE DECODE(1, 0, (SELECT COUNT(*) from tbl
symfony - 奏鸣曲管理包 : strange with labels
我已经在 symfony 2.1 上安装了最新的 Sonata 管理包，但遇到了以下问题: 配置文件: services: app.geo.admin.city: class: App
PHP - 图像输出 : strange string
我必须输出一系列先前保存在数据库中的随机图像。在输出的那一刻，而不是打印一张图片，代码打印一个奇怪的字符串(meaby dumpfile？): (¢Š(¢Š(¢Š(¢Š(¢Š(¢Š(¢Š(¢Š(¢Š(
c# - "Strange"C#语法
我刚刚在从 Code Project 下载的项目中看到了这个: base.DialogResult = this.Result != null; 我不认为自己是 C# 新手，但这个对我来说是新手。谁能
java - 类型转换和包装器 : some strange cases
看看这个...今天晚上我试图将一些 primiteves 转换到 wrapper 上时发现: Integer i = (Integer)4; Integer i = (Integer)4f; // D
python - 在函数内分配变量 : Strange behaviour
我很少使用 Python，所以我不清楚为什么允许这样的行为:没有 w 对象，因此它没有 s 属性，那为什么 f 允许进行 w.s 赋值？ >>> def f(): w.s="ads" #al
Jquery 克隆和单选按钮 : strange behavior
在 Jsfiddle 上:http://jsfiddle.net/jhzux/ 我在这个简单的脚本上浪费了很多时间。我想做的是在 jQuery 中启用克隆表单，然后使它们正常工作。首先，当我在 Js
javascript - 为什么会:after be drawed strangely?
这是我的代码: .specific_tag_cases a:after{ position: absolute; font-family: Arial; background-

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

postgresql - Postgres : strange behavior with optimistic locking